Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Search Sentry Docs

search_docs
Read-only

Find Sentry documentation for SDK setup, framework integrations, instrumentation, and configuration like sampling, data scrubbing, and source maps; returns matching page paths and snippets.

Instructions

Search Sentry documentation for SDK setup, framework integrations, instrumentation, and configuration such as sampling, data scrubbing, and source maps. Returns matching page paths and snippets only. Use the Sentry tool get_doc to read a full 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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
guideNoLimit results to a platform (`python`) or platform/guide (`javascript/nextjs`).
queryYesNatural-language query. Name the SDK option or feature when you know it, such as `beforeSend` or `tracesSampleRate`.
maxResultsNoMaximum results to return.

Output Schema

NameRequiredDescriptionDefault
guideYes
queryYes
resultsYes
suggestedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that results are paths and snippets only, warning the agent not to expect full page content. It stops short of mentioning ranking or empty-result behavior, so it is not exhaustive.

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?

Three short sentences, front-loaded with the purpose, then the return constraint, then the alternative. Every sentence carries distinct information with no repetition of the title or schema.

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

Completeness5/5

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

For a read-only documentation search with a fully documented three-parameter schema, an output schema, and clear annotations, nothing an agent needs to call it correctly is missing. Purpose, routing to get_doc, and the snippet-only return nature are all stated.

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 schema itself already instructs the agent to name SDK options like `beforeSend` or `tracesSampleRate` and explains the guide and maxResults bounds. The description only adds topical scope ('SDK setup, framework integrations, instrumentation'), which is marginally useful context but not parameter-specific meaning. 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?

The description gives a specific verb and resource ('Search Sentry documentation') and enumerates the content domain: SDK setup, framework integrations, instrumentation, sampling, data scrubbing, source maps. That scope cleanly separates it from the data-oriented siblings such as search_issues or search_errors without the agent needing to open any schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: 'Use the Sentry tool `get_doc` to read a full page,' which names the alternative and the condition that selects it. Combined with 'Returns matching page paths and snippets only,' the agent knows this is a discovery step, not a content-retrieval step.

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