Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_list_projects

Retrieve all projects within your Sentry organization to monitor error tracking, performance metrics, and application health status.

Instructions

List all projects in the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main execution handler for the sentry_list_projects tool. Validates API client availability, fetches projects via apiClient.listProjects(), and returns a formatted list of projects.
    case "sentry_list_projects": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const projects = await apiClient.listProjects();
      
      return {
        content: [
          {
            type: "text",
            text: `Found ${projects.length} projects:\n${projects.map((p: any) => `- ${p.slug}: ${p.name}`).join('\n')}`,
          },
        ],
      };
    }
  • src/index.ts:390-396 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and input schema (empty object).
      name: "sentry_list_projects",
      description: "List all projects in the organization",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper method in SentryAPIClient that performs the actual API request to retrieve the list of projects for the organization.
    async listProjects() {
      return this.request(`/organizations/${this.org}/projects/`);
    }
  • Private request method used by listProjects to make authenticated HTTP requests to the Sentry API.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying it's read-only, but doesn't specify whether it requires authentication, returns paginated results, or has any rate limits. This leaves significant gaps for a tool that interacts with an external API.

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, clear sentence that directly states the tool's purpose without any fluff or unnecessary details. It's front-loaded and efficiently communicates the core functionality, making it easy for an agent to parse quickly.

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 simplicity (0 parameters, no output schema), the description is adequate as a basic read operation. However, without annotations or output schema, it lacks details on authentication requirements, return format, or error handling, which are important for API tools. It meets minimum viability but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, which is correct for a parameterless tool, earning a high score as it doesn't create confusion or redundancy.

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 ('List') and resource ('projects in the organization'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling list tools like sentry_list_issues or sentry_list_releases, which would require specifying what makes listing projects different from listing other resources.

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 like authentication, nor does it differentiate from other list operations in the sibling set, leaving the agent to infer usage context purely from the tool name.

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