feat(tools): Add find_dropped_events tool for the events-dropped endpoint - #1410
Open
manessaraj wants to merge 4 commits into
Open
manessaraj wants to merge 4 commits into
manessaraj wants to merge 4 commits into
Conversation
manessaraj
force-pushed
the
sarajmanes/dain-1863-mcp-dropped-events-tool
branch
from
October 5, 2026 16:11
46bd05f to
556cbc5
Compare
manessaraj
marked this pull request as ready for review
October 5, 2026 19:35
…oint Exposes Sentry's dedicated events-dropped endpoint to agents as a new find_dropped_events tool: ground-truth data-fidelity information (what Sentry received but dropped, and why) bucketed over time, alongside accepted volume so a caller can compute the dropped share. Surfaced directly (same tier as search_events) since an agent debugging a flat/spiky/low chart should be able to reach it without discovery. - api-client: getDroppedEvents() + DroppedEvents response schemas - tool: find_dropped_events (datasets: spans, logs, metrics) - registered in the catalog + direct surface; regenerated definitions Backed by an agent eval: naive agents given a user-phrased question reliably discovered and called this tool, and attributed flat/spiky charts to the right drop reason — where the same agents without it concluded "nothing is broken." Refs DAIN-1863
Remove doc comments that restated project framing / dev decisions rather than explaining non-obvious code. Matches the surrounding file convention, where sibling schemas, client methods, and tools carry no such comments. The caller-facing tool description and param descriptions are unchanged. Refs DAIN-1863
Three targeted edits to the tool description, keeping the tested structure: - Lead with what the tool captures (dropped before storage), not "received" — SDK-side drops (sample_rate, before_send) never reach Sentry. - Frame charts as one example of an accepted-only view, not the purpose; the tool's role is ground-truth data fidelity: is the data in Sentry or dropped. - Reframe the trust bullet around confirming data is actually in Sentry before relying on a query, aggregate, or dashboard. Regenerated tool/skill definitions. Refs DAIN-1863
Adding find_dropped_events to TOP_LEVEL_TOOL_NAMES changes the exact direct tool set these guardrail tests assert, so add it to DEFAULT_DIRECT_TOOL_NAMES. The catalog-search test queried 'event stacktrace' at limit 5; find_dropped_events now ranks there (its name contains 'events'), so raise the limit to 8 to keep asserting that catalog-only tools remain findable via search. Refs DAIN-1863
manessaraj
force-pushed
the
sarajmanes/dain-1863-mcp-dropped-events-tool
branch
from
October 5, 2026 20:04
7eb699a to
143768d
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
find_dropped_eventstool that exposes Sentry's dedicated events-dropped endpoint to agents. It returns ground-truth data-fidelity information — what Sentry received but dropped (rate limited, over quota, filtered, invalid, abuse/spike protection, client-discarded viasample_rate/before_send, cardinality limited) — bucketed over time, plus the accepted volume per bucket so a caller can compute the dropped share.Refs DAIN-1863