Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Event Attachment

get_event_attachment
Read-only

List or download Sentry event attachments, including screenshots, log files, and minidumps, to inspect files uploaded with an error report.

Instructions

List or download the attachments of a Sentry event, such as screenshots, log files, and minidumps uploaded with an error report.

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": {
      "projectSlug": "<projectSlug>",
      "eventId": "<eventId>"
    },
    "name": "get_event_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
eventIdYesThe 32-character hex event ID.
regionUrlNo
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
attachmentIdNoThe attachment to download. Omit to list the event's attachments.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully discloses the two-mode behavior and the kinds of artifacts involved, but says nothing about binary payloads, size limits, or how downloads are returned, which matters for a tool whose output can be a file rather than JSON.

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

Conciseness5/5

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

A single sentence with the verb and resource front-loaded and zero filler. The examples are placed where they clarify scope rather than pad the text.

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

Completeness3/5

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

With six parameters, no output schema, and 83% schema coverage, the description leaves the return behavior undefined: an agent cannot tell whether listing yields a JSON array of attachments or whether download emits binary/base64 content. Flagging that distinction is the main missing piece for a tool of this complexity.

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%, so the schema already explains eventId, projectSlug, organizationSlug, regionUrl, fresh, and the attachmentId omit-to-list rule. The description adds only a light gloss on the list/download split and does not enrich any parameter beyond the schema text; baseline 3 applies.

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

Purpose4/5

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

The description uses a specific verb pair (list/download) plus a specific resource (attachments of a Sentry event), and it names concrete examples (screenshots, log files, minidumps) so an agent understands what payload this returns. It is clear against siblings such as get_event_stacktrace, though it doesn't explicitly contrast itself with any of them.

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

Usage Guidelines3/5

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

Usage guidance is only implied: the agent can infer this is for inspecting an event's uploaded artifacts during debugging. There is no explicit 'use when' statement, no prerequisites, and no statement of when the listing mode versus the download mode is appropriate beyond the bare 'List or download' phrase.

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