Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Sentry Doc

get_doc
Read-only

Fetch a Sentry documentation page's full markdown content using a path from search results or a docs.sentry.io URL so AI assistants can read and use the details.

Instructions

Fetch the full markdown content of a Sentry documentation page.

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": {
      "path": "<path>"
    },
    "name": "get_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDocs page path from search_docs, or a full docs.sentry.io page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description usefully clarifies that the return is the full markdown content, but it says nothing about error behavior, truncation, or external fetch characteristics beyond the openWorld annotation.

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?

The description is a single front-loaded sentence with zero unnecessary wording. Every phrase earns its place for this simple fetch tool.

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?

For a one-parameter read-only documentation fetch with annotations covering safety and no output schema, the description is mostly complete. The remaining gap is minor: it does not describe failure behavior for invalid or unreachable documentation paths.

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 100%, and the path parameter is already documented as coming from search_docs or a full docs.sentry.io URL. The description adds no parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: fetch the full markdown content of a Sentry documentation page. It is clearly distinguishable from the sibling resource/issue/monitor tools, but it does not explicitly name or differentiate itself from documentation-search behavior.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, no alternatives, and no exclusions. The schema hints that the path can come from search_docs, but the description itself does not explain that workflow or when not to use this tool.

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