Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_set_release

Configure release version for Sentry's health tracking to monitor application performance and error rates by version.

Instructions

Set the release version for release health tracking

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
releaseYesRelease version (e.g., 'myapp@1.0.0')
distNoDistribution identifier

Implementation Reference

  • src/index.ts:337-354 (registration)
    Tool registration including name, description, and input schema for 'sentry_set_release'.
    {
      name: "sentry_set_release",
      description: "Set the release version for release health tracking",
      inputSchema: {
        type: "object",
        properties: {
          release: {
            type: "string",
            description: "Release version (e.g., 'myapp@1.0.0')",
          },
          dist: {
            type: "string",
            description: "Distribution identifier",
          },
        },
        required: ["release"],
      },
    },
  • Handler function for 'sentry_set_release' tool that sets the release and dist tags in Sentry using Sentry.setTag.
    case "sentry_set_release": {
      const { release, dist } = args as any;
      
      // Set release globally
      Sentry.setTag("release", release);
      if (dist) {
        Sentry.setTag("dist", dist);
      }
      
      return {
        content: [
          {
            type: "text",
            text: `Release set to: ${release}${dist ? ` (dist: ${dist})` : ''}`,
          },
        ],
      };
    }
  • Input schema definition for the 'sentry_set_release' tool, specifying parameters for release and optional dist.
    inputSchema: {
      type: "object",
      properties: {
        release: {
          type: "string",
          description: "Release version (e.g., 'myapp@1.0.0')",
        },
        dist: {
          type: "string",
          description: "Distribution identifier",
        },
      },
      required: ["release"],
    },
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 of behavioral disclosure. While 'Set' implies a mutation operation, the description doesn't specify whether this requires specific permissions, what happens if the release doesn't exist, whether it's idempotent, or how it affects tracking. For a mutation tool with zero annotation coverage, this is inadequate.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the complexity (a mutation tool for release tracking), lack of annotations, no output schema, and incomplete behavioral context, the description is insufficient. It should explain more about the operation's effects, error conditions, or typical use cases to compensate for the missing structured data.

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 ('release' and 'dist') with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, such as format examples for 'dist' or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Set') and the target ('release version for release health tracking'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this from sibling tools like 'sentry_create_release' or 'sentry_list_releases', which would require more specific context about when to use each.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether a release must exist first), context (e.g., during deployment or error tracking), or exclusions (e.g., not for creating releases). With multiple sibling tools related to releases, this lack of differentiation is a significant gap.

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