Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_add_breadcrumb

Add debugging breadcrumbs to track application flow and errors in Sentry for Cursor, providing context for troubleshooting issues.

Instructions

Add a breadcrumb for debugging context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesBreadcrumb message
categoryNoCategory of the breadcrumb
levelNoSeverity levelinfo
dataNoAdditional data for the breadcrumb

Implementation Reference

  • The handler function that implements the sentry_add_breadcrumb tool by calling Sentry.addBreadcrumb with the provided message, category, level (mapped), data, and current timestamp.
    case "sentry_add_breadcrumb": {
      const { message, category, level = "info", data } = args as any;
      
      Sentry.addBreadcrumb({
        message,
        category,
        level: mapSeverityLevel(level),
        data,
        timestamp: Date.now() / 1000,
      });
      
      return {
        content: [
          {
            type: "text",
            text: `Breadcrumb added: ${message}`,
          },
        ],
      };
    }
  • The input schema for the sentry_add_breadcrumb tool, defining parameters: message (required), category, level (default 'info'), and data.
    inputSchema: {
      type: "object",
      properties: {
        message: {
          type: "string",
          description: "Breadcrumb message",
        },
        category: {
          type: "string",
          description: "Category of the breadcrumb",
        },
        level: {
          type: "string",
          enum: ["fatal", "error", "warning", "info", "debug"],
          description: "Severity level",
          default: "info",
        },
        data: {
          type: "object",
          description: "Additional data for the breadcrumb",
          additionalProperties: true,
        },
      },
      required: ["message"],
    },
  • src/index.ts:165-193 (registration)
    The tool registration in the ListTools response, including name, description, and inputSchema for sentry_add_breadcrumb.
    {
      name: "sentry_add_breadcrumb",
      description: "Add a breadcrumb for debugging context",
      inputSchema: {
        type: "object",
        properties: {
          message: {
            type: "string",
            description: "Breadcrumb message",
          },
          category: {
            type: "string",
            description: "Category of the breadcrumb",
          },
          level: {
            type: "string",
            enum: ["fatal", "error", "warning", "info", "debug"],
            description: "Severity level",
            default: "info",
          },
          data: {
            type: "object",
            description: "Additional data for the breadcrumb",
            additionalProperties: true,
          },
        },
        required: ["message"],
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read/write operation, its side effects (e.g., whether it sends data immediately or batches), permissions needed, or rate limits. This is inadequate for a tool that likely modifies debugging state.

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 a single, efficient sentence that gets straight to the point without unnecessary words. However, it's overly brief and could benefit from more context to be truly helpful, slightly reducing its effectiveness.

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

Completeness2/5

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

Given no annotations, no output schema, and a tool that likely involves mutation (adding data), the description is incomplete. It lacks details on behavior, return values, or how it integrates with sibling tools, making it insufficient for safe and effective use by an AI agent.

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 fully documents parameters like message, category, level, and data. The description adds no additional meaning beyond implying these are for 'debugging context,' which is already inferred from the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Add a breadcrumb') and purpose ('for debugging context'), which is clear but vague. It doesn't specify what a breadcrumb is in the Sentry context or how it differs from sibling tools like sentry_set_context or sentry_set_tag, which also add debugging information.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention when breadcrumbs are appropriate compared to other debugging tools like sentry_capture_exception or sentry_set_context, leaving the agent to infer usage from the name alone.

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