Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_get_event

Retrieve a specific Sentry event from an issue using project slug and event ID for detailed error analysis and debugging.

Instructions

Retrieve a specific Sentry event from an issue. Requires issue ID/URL and event ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectSlugYesProject slug/identifier
eventIdYesEvent ID

Implementation Reference

  • The main handler for the 'sentry_get_event' tool. It validates the apiClient, extracts parameters, calls apiClient.getEvent(projectSlug, eventId), and returns a formatted text response with event details.
    case "sentry_get_event": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { projectSlug, eventId } = args as any;
      const event = await apiClient.getEvent(projectSlug, eventId);
      
      return {
        content: [
          {
            type: "text",
            text: `Event ${eventId} details:\n` +
              `- Title: ${event.title}\n` +
              `- Message: ${event.message}\n` +
              `- Platform: ${event.platform}\n` +
              `- Date: ${event.dateCreated}\n` +
              `- User: ${event.user ? JSON.stringify(event.user) : 'N/A'}\n` +
              `- Tags: ${JSON.stringify(event.tags)}`,
          },
        ],
      };
    }
  • The tool definition including name, description, and input schema (JSON Schema for parameters: projectSlug and eventId). This is part of the tools array registered with the MCP server.
    {
      name: "sentry_get_event",
      description: "Retrieve a specific Sentry event from an issue. Requires issue ID/URL and event ID.",
      inputSchema: {
        type: "object",
        properties: {
          projectSlug: {
            type: "string",
            description: "Project slug/identifier",
          },
          eventId: {
            type: "string",
            description: "Event ID",
          },
        },
        required: ["projectSlug", "eventId"],
      },
    },
  • The helper method in SentryAPIClient that performs the actual API request to fetch the event from Sentry's REST API.
    async getEvent(projectSlug: string, eventId: string) {
      return this.request(`/projects/${this.org}/${projectSlug}/events/${eventId}/`);
    }
  • src/index.ts:690-690 (registration)
    The registration of all tools including 'sentry_get_event' via server.setTools(tools), where tools array contains the schema entry.
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Retrieve' and requirements but doesn't disclose behavioral traits such as whether this is a read-only operation, error handling, rate limits, or authentication needs. The description adds minimal context beyond the basic action, leaving significant gaps in transparency.

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, efficient sentence that front-loads the main action ('Retrieve a specific Sentry event') and includes essential prerequisites. There's no wasted text, and it's appropriately sized for a simple retrieval tool.

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 complexity (simple retrieval with 2 parameters), 100% schema coverage, and no output schema, the description is adequate but incomplete. It covers the basic purpose and requirements but lacks details on behavior, error cases, or output format, which could hinder an agent's ability to use it effectively without trial and error.

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%, so the schema already documents both parameters ('projectSlug' and 'eventId'). The description adds value by implying a relationship to an issue ('from an issue') and stating requirements, but it doesn't provide additional meaning like format details or usage examples beyond what the schema specifies. This meets the baseline for 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 action ('Retrieve') and resource ('specific Sentry event from an issue'), making the purpose understandable. It distinguishes from siblings like 'sentry_get_issue' by focusing on events rather than issues, though it doesn't explicitly contrast them. The mention of 'issue ID/URL' is slightly misleading since the input schema uses 'projectSlug' and 'eventId', not an issue ID.

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 by stating 'Requires issue ID/URL and event ID,' which suggests prerequisites but doesn't specify when to use this tool versus alternatives like 'sentry_list_issue_events' or 'sentry_get_issue.' There's no explicit guidance on context or exclusions, leaving usage somewhat open-ended.

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