Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_resolve_short_id

Retrieve issue details, project context, and status by entering a short ID like PROJ-123 to quickly access Sentry error information.

Instructions

Retrieve details about an issue using its short ID. Maps short IDs to issue details, project context and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shortIdYesThe short ID of the issue (e.g., 'PROJ-123')

Implementation Reference

  • MCP server tool handler for sentry_resolve_short_id. Extracts shortId argument, calls apiClient.resolveShortId(), and returns formatted issue details as text content.
    case "sentry_resolve_short_id": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { shortId } = args as any;
      const result = await apiClient.resolveShortId(shortId);
      
      return {
        content: [
          {
            type: "text",
            text: `Issue resolved from short ID ${shortId}:\n` +
              `- Issue ID: ${result.groupId}\n` +
              `- Project: ${result.projectSlug}\n` +
              `- Organization: ${result.organizationSlug}\n` +
              `- Title: ${result.group.metadata.title}\n` +
              `- Status: ${result.group.status}\n` +
              `- Level: ${result.group.level}\n` +
              `- First seen: ${result.group.firstSeen}\n` +
              `- Last seen: ${result.group.lastSeen}`,
          },
        ],
      };
    }
  • src/index.ts:516-528 (registration)
    Tool registration in ListTools response, including name, description, and input schema definition.
      name: "sentry_resolve_short_id",
      description: "Retrieve details about an issue using its short ID. Maps short IDs to issue details, project context and status.",
      inputSchema: {
        type: "object",
        properties: {
          shortId: {
            type: "string",
            description: "The short ID of the issue (e.g., 'PROJ-123')",
          },
        },
        required: ["shortId"],
      },
    },
  • Core helper method in SentryAPIClient that resolves a short ID by making an authenticated GET request to Sentry's /organizations/{org}/shortids/{shortId}/ API endpoint.
      return this.request(`/organizations/${this.org}/shortids/${shortId}/`);
    }
  • Private request method used by all API calls, including resolveShortId, handling authentication, fetch, error checking, and JSON parsing.
    private async request(endpoint: string, options: any = {}) {
      const url = `${this.baseUrl}${endpoint}`;
      const response = await fetch(url, {
        ...options,
        headers: {
          'Authorization': `Bearer ${this.authToken}`,
          'Content-Type': 'application/json',
          ...options.headers,
        },
      });
    
      if (!response.ok) {
        throw new Error(`Sentry API error: ${response.status} ${response.statusText}`);
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions retrieving details, project context, and status, which gives some behavioral insight, but lacks critical information such as whether this is a read-only operation, error handling for invalid IDs, rate limits, or authentication requirements. For a tool with no annotations, this is insufficient disclosure.

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?

The description is concise with two sentences that efficiently convey the tool's purpose and mapping function. It is front-loaded with the main action and avoids unnecessary details. However, it could be slightly more structured by explicitly separating usage guidance, but overall it earns its place without waste.

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?

Given the tool's low complexity (1 parameter, no nested objects) and high schema coverage, the description is somewhat complete but lacks depth. No output schema exists, so the description should ideally explain return values more clearly (e.g., what 'issue details' include). It covers basics but misses behavioral and output context, making it adequate but with gaps.

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%, with the parameter 'shortId' well-documented in the schema. The description adds marginal value by reinforcing the mapping purpose and providing an example format ('e.g., 'PROJ-123''), but does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 clearly states the verb ('Retrieve details') and resource ('about an issue'), and specifies the key input ('using its short ID'). It distinguishes from siblings like sentry_get_issue by focusing on short ID mapping, though not explicitly naming alternatives. However, it lacks explicit sibling differentiation, keeping it at 4 rather than 5.

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?

The description implies usage context by mentioning 'Maps short IDs to issue details', suggesting this tool is for resolving short IDs when they are available. However, it does not explicitly state when to use this vs. alternatives like sentry_get_issue or sentry_list_issues, nor does it provide exclusions or prerequisites, leaving usage somewhat inferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/diegofornalha/sentry-mcp-cursor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server