Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

get_organization

Retrieve organization details from the Glitchtip error tracking platform to access essential information for monitoring and debugging workflows.

Instructions

Get organization details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that fetches the organization details from the Glitchtip API endpoint and returns it as JSON text content.
    async getOrganization() {
      const url = `${this.apiEndpoint}/api/0/organizations/${this.organizationSlug}/`;
      
      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 organization: ${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 tool schema definition in the list of tools, specifying name, description, and empty input schema.
    {
      name: "get_organization",
      description: "Get organization details",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • src/index.js:147-148 (registration)
    Registration in the CallToolRequestSchema switch statement that dispatches to the handler.
    case "get_organization":
      return await this.getOrganization();
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. 'Get organization details' implies a read-only operation, but it doesn't specify authentication needs, rate limits, error conditions, or what the return format looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 with no wasted words. It's front-loaded with the core action and resource. However, it could be slightly more informative without losing conciseness, such as specifying the type of details (e.g., 'Get metadata and settings for the organization').

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 simple tool with 0 parameters, the description is incomplete. It doesn't explain what 'details' includes, how the data is returned, or any behavioral aspects like permissions. For a tool that might return critical organizational info, more context is needed to guide effective use.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any parameter gaps, and it correctly implies no inputs are required. Baseline is 4 for zero parameters, as it avoids misleading param info.

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 'Get organization details' states the action (get) and resource (organization details), which provides a basic purpose. However, it's vague about what 'details' specifically includes and doesn't differentiate from sibling tools like get_issue or get_project, which follow a similar 'get [resource]' pattern. It avoids tautology but lacks specificity.

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. With siblings like list_teams or list_projects that might retrieve related data, there's no indication of whether this tool is for high-level organization metadata, configuration, or other purposes. No exclusions or prerequisites are mentioned.

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