Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

get_project

Retrieve detailed information about a specific Glitchtip project using its unique slug identifier for error monitoring and project management.

Instructions

Get details of a specific Glitchtip project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_slugYesThe slug of the project to retrieve

Implementation Reference

  • The handler function that implements the 'get_project' tool logic. It takes a project_slug argument, fetches the project details from the Glitchtip API, and returns the JSON data or an error message.
    async getProject(args) {
      const { project_slug } = args;
      
      if (!project_slug) {
        return {
          content: [
            {
              type: "text",
              text: "Error: project_slug is required"
            }
          ]
        };
      }
      
      const url = `${this.apiEndpoint}/api/0/projects/${this.organizationSlug}/${project_slug}/`;
      
      try {
        const response = await fetch(url, {
          method: 'GET',
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Accept': 'application/json'
          }
        });
        
        if (!response.ok) {
          const errorText = await response.text();
          return {
            content: [
              {
                type: "text",
                text: `Error fetching project: ${response.status} ${response.statusText}\n${errorText}`
              }
            ]
          };
        }
        
        const data = await response.json();
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error: ${error.message}`
            }
          ]
        };
      }
    }
  • The schema definition for the 'get_project' tool, including name, description, and input schema requiring 'project_slug'.
    {
      name: "get_project",
      description: "Get details of a specific Glitchtip project",
      inputSchema: {
        type: "object",
        properties: {
          project_slug: {
            type: "string",
            description: "The slug of the project to retrieve"
          }
        },
        required: ["project_slug"]
      }
    },
  • src/index.js:145-146 (registration)
    The registration/dispatch case in the CallToolRequest handler that routes calls to the getProject method.
    case "get_project":
      return await this.getProject(args);
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. While 'Get details' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data, or what happens with invalid project slugs. The description adds minimal behavioral context beyond the basic operation.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a single-parameter read tool with good schema coverage but no annotations or output schema, the description is minimally adequate. It states what the tool does but lacks important context about authentication requirements, error conditions, return format, and differentiation from sibling tools.

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 the single parameter 'project_slug' adequately. The description doesn't add any additional parameter context beyond what's in the schema, such as format examples or where to find project slugs. Baseline 3 is appropriate when schema does the documentation work.

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 ('Get details') and target resource ('a specific Glitchtip project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'list_projects' or explain what distinguishes 'getting details' from 'listing' projects.

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 like 'list_projects' or 'get_issue'. It doesn't mention prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage patterns.

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/CleverMobi/glitchtip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server