Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Sentry MCP Info

get_sentry_mcp_info
Read-only

Retrieve the running Sentry MCP server’s version and details to verify compatibility with skills or integrations before connecting.

Instructions

Get the version and details of the running Sentry MCP server, e.g. to check compatibility with a skill or integration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sentry_mcp_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
versionYesThe Sentry MCP server version.

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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the result describes the *running* server (i.e. live process state, not stored config), which is meaningful context beyond the annotations; the output schema carries the return-value detail.

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 action and object front-loaded and the motivating example trailing as a qualifier. No filler and nothing redundant with structured fields.

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 zero-arg, read-only, closed-world tool with an output schema and full annotation coverage, the description says everything an agent needs to decide to call it. Only marginal value would come from explicitly stating it requires no arguments and returns server metadata rather than Sentry data.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing the description could add. No parameter claims are made or needed.

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?

Specific verb ('Get') plus a precisely scoped resource ('version and details of the running Sentry MCP server'). The resource is metadata about the server itself, which cleanly sets it apart from the sibling tools that all read Sentry domain objects, though the description never explicitly contrasts with them.

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?

Provides a concrete when-to-use case - checking compatibility with a skill or integration - which is enough for a zero-parameter introspection tool. It does not name an alternative or state when not to call it, but there is no plausible competing tool for this purpose.

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