Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Event Stacktrace

get_event_stacktrace
Read-only

Retrieve the full stack trace for a specific thread in a Sentry event, including non-crashed threads. Lists available threads when no match or multiple matches occur.

Instructions

Get the full stack trace (stacktrace) of one thread in a Sentry event, such as a non-crashed thread listed in the issue details. Lists the threads when the selector matches none or several. For an event with no threads, returns its event-level stacktrace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueId": "<issueId>"
    },
    "name": "get_event_stacktrace"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
threadNoNumeric thread ID or exact thread name from the issue details. Omit for Sentry's default: the crashed thread, else the first with a stack trace.
eventIdNoAn event ID in the issue, or `latest`.latest
issueIdYesThe issue short ID, e.g. `PROJECT-1Z43`.
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
threadYesThe selected thread and its stacktrace.
eventIdYes
issueIdYes
platformYesThe event platform, which sets how to read frames.
selectionYes
stacktraceYesThe event-level stacktrace, when the event has no threads but has a stack outside them, as on a captured message.
threadCountYes
availableThreadsYesEvery thread on the event, listed only when the `thread` selector matched none or several.
organizationSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's added value is the two fallback behaviors: it lists threads when the selector matches none or several, and returns the event-level stacktrace when the event has no threads. That variable return shape is the key non-obvious trait and it is disclosed clearly, though nothing is said about auth or result size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose before the fallback semantics. Every sentence carries information, with only minor redundancy in the '(stacktrace)' gloss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description needn't explain return values, and it correctly spends its words on the ambiguous part: which thread is selected and what happens when selection fails. Nothing essential for a correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 83%, and the schema already explains the thread selector, its default, and the eventId/issueId formats in detail. The description reinforces only that the selector targets a single thread; it adds no new syntax or format meaning beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: 'Get the full stack trace of one thread in a Sentry event'. The phrase 'one thread' immediately differentiates it from issue-level or event-level fetch tools in the sibling set, and the parenthetical '(stacktrace)' disambiguates terminology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage cue: 'such as a non-crashed thread listed in the issue details', which tells the agent when this tool is the right pick over a crashed-thread default. It stops short of naming an alternative tool or stating when not to call it, so it lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.