Skip to main content
Glama
c20020207

AppSignal MCP Server

by c20020207

getIncident

Fetch detailed incident information by providing a valid incident number using the Model Context Protocol server connected to AppSignal monitoring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incidentNumberYes

Implementation Reference

  • Registration of the MCP 'getIncident' tool, including input schema validation with Zod and the handler function that calls AppSignalClient.getIncident and formats the response as text content.
    this.server.tool(
      'getIncident',
      {
        incidentNumber: z.number().int().positive(),
      },
      async ({ incidentNumber }) => {
        try {
          const incident = await this.client.getIncident(incidentNumber);
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(incident, null, 2),
            }],
          };
        } catch (error) {
          if (error instanceof Error) {
            return {
              content: [{
                type: 'text',
                text: `Error fetching incident: ${error.message}`,
              }],
              isError: true,
            };
          }
          throw error;
        }
      }
    );
  • Core handler logic in AppSignalClient that executes GraphQL query to fetch incident details from AppSignal API.
    async getIncident(incidentNumber: number): Promise<Incident> {
      const query = `
        query IncidentQuery($appId: String!, $incidentNumber: Int!) {
          app(id: $appId) {
            id
            incident(incidentNumber: $incidentNumber) {
              ... on ExceptionIncident {
                id
                number
                count
                lastOccurredAt
                actionNames
                exceptionName
                state
                namespace
                firstBacktraceLine
                errorGroupingStrategy
                severity
              }
            }
          }
        }
      `;
    
      const result = await this.executeQuery<{
        app: {
          id: string;
          incident: Incident;
        };
      }>(query, {
        appId: this.appId,
        incidentNumber,
      });
    
      return result.app.incident;
    }
  • Zod schema defining the structure of Incident data returned by getIncident.
    export const IncidentSchema = z.object({
      id: z.string(),
      number: z.number(),
      count: z.number(),
      lastOccurredAt: z.string(),
      actionNames: z.array(z.string()),
      exceptionName: z.string(),
      state: z.string(),
      namespace: z.string(),
      firstBacktraceLine: z.string().optional(),
      errorGroupingStrategy: z.string().optional(),
      severity: z.string().optional(),
    });
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/c20020207/mcp-appsignal'

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