Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_start_transaction

Start performance monitoring transactions to track application operations like HTTP requests and database queries for error detection and optimization.

Instructions

Start a performance monitoring transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTransaction name
opYesOperation type (e.g., 'http.request', 'db.query')
descriptionNoTransaction description

Implementation Reference

  • Handler for the 'sentry_start_transaction' tool. Extracts parameters, ends any existing transaction, starts a new Sentry span (transaction) using Sentry.startSpan, stores it in currentTransaction, and returns a confirmation message.
    case "sentry_start_transaction": {
      const { name: transactionName, op, description } = args as any;
      
      if (currentTransaction) {
        currentTransaction.end();
      }
      
      currentTransaction = Sentry.startSpan(
        { name: transactionName, op },
        () => {
          // Transaction is active here
          return null;
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: `Transaction started: ${transactionName} (${op})`,
          },
        ],
      };
    }
  • src/index.ts:260-281 (registration)
    Registration of the 'sentry_start_transaction' tool in the ListTools response, including name, description, and input schema definition.
    {
      name: "sentry_start_transaction",
      description: "Start a performance monitoring transaction",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Transaction name",
          },
          op: {
            type: "string",
            description: "Operation type (e.g., 'http.request', 'db.query')",
          },
          description: {
            type: "string",
            description: "Transaction description",
          },
        },
        required: ["name", "op"],
      },
    },
  • Input schema definition for the 'sentry_start_transaction' tool, specifying required 'name' and 'op' parameters with optional 'description'.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Transaction name",
        },
        op: {
          type: "string",
          description: "Operation type (e.g., 'http.request', 'db.query')",
        },
        description: {
          type: "string",
          description: "Transaction description",
        },
      },
      required: ["name", "op"],
    },
  • Global variable used to track the current active transaction/span for coordination between start and finish transactions.
    let currentTransaction: any | null = null;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Start a performance monitoring transaction' implies this initiates something, but doesn't reveal whether this creates resources, requires specific permissions, has side effects, or how the transaction interacts with other tools. No information about what happens after starting or typical response patterns.

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, focused sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the essential information and contains zero redundant or extraneous content.

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?

For a tool that presumably creates or initiates monitoring transactions (implied by 'start'), the description is insufficient given no annotations and no output schema. It doesn't explain what a transaction is, how it relates to other Sentry operations, what happens after starting, or what the agent should expect as a result.

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 all three parameters with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 ('Start') and resource ('performance monitoring transaction'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'sentry_finish_transaction' or explain what a 'performance monitoring transaction' entails in the Sentry context.

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 about when to use this tool versus alternatives like 'sentry_finish_transaction' or other monitoring tools. The description gives no context about prerequisites, typical workflows, or when this operation is appropriate versus other Sentry operations.

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