Skip to main content
Glama
cloudbring

New Relic MCP Server

by cloudbring

acknowledge_incident

Acknowledge an open incident by providing its ID to update its status and indicate it is being addressed.

Instructions

Acknowledge an open incident

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incident_idYesThe ID of the incident to acknowledge

Implementation Reference

  • Schema definition for acknowledge_incident tool with required incident_id parameter
    getAcknowledgeTool(): Tool {
      return {
        name: 'acknowledge_incident',
        description: 'Acknowledge an open incident',
        inputSchema: {
          type: 'object',
          properties: {
            incident_id: {
              type: 'string',
              description: 'The ID of the incident to acknowledge',
            },
          },
          required: ['incident_id'],
        },
      };
    }
  • Handler that builds a GraphQL mutation to acknowledge an incident via aiIssuesAcknowledge and returns the acknowledged issue
    async acknowledgeIncident(input: {
      incident_id: string;
      comment?: string;
    }): Promise<Record<string, unknown> | null> {
      const mutation = `
        mutation {
          aiIssuesAcknowledge(
            issueIds: ["${input.incident_id}"]
            ${input.comment ? `, comment: "${input.comment}"` : ''}
          ) {
            issues {
              issueId
              state
              acknowledgedAt
              acknowledgedBy
              ${input.comment ? 'comment' : ''}
            }
            errors {
              type
              description
            }
          }
        }
      `;
    
      const response = await this.client.executeNerdGraphQuery<{
        aiIssuesAcknowledge?: {
          issues?: Record<string, unknown>[];
          errors?: Array<{ description?: string }>;
        };
      }>(mutation);
      const result = response.data?.aiIssuesAcknowledge;
    
      if (result?.errors && result.errors.length > 0) {
        throw new Error(result.errors[0].description);
      }
    
      return result?.issues?.[0] || null;
    }
  • src/server.ts:76-77 (registration)
    Tool registration in the server's registerTools method via alertTool.getAcknowledgeTool()
    alertTool.getAcknowledgeTool(),
    syntheticsTool.getListMonitorsTool(),
  • src/server.ts:215-227 (registration)
    Execution dispatch in server.ts that validates input and delegates to AlertTool.acknowledgeIncident
    case 'acknowledge_incident': {
      const { incident_id, comment } = args as Record<string, unknown>;
      if (typeof incident_id !== 'string' || incident_id.trim() === '') {
        throw new Error('acknowledge_incident: "incident_id" (non-empty string) is required');
      }
      if (comment !== undefined && typeof comment !== 'string') {
        throw new Error('acknowledge_incident: "comment" must be a string when provided');
      }
      return await new AlertTool(this.client).acknowledgeIncident({
        incident_id,
        comment: comment as string | undefined,
      });
    }
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 transparency. It only states 'acknowledge' without detailing side effects (e.g., state changes, notifications) or permissions needed. This is insufficient for an action that likely modifies state.

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. However, it could incorporate additional useful context without becoming verbose. Still, it is appropriately sized for a simple tool.

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 output schema and lack of behavioral details, the description is incomplete. It does not explain return values (e.g., success confirmation, error messages) or authentication/authorization prerequisites, leaving the agent underinformed.

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?

The schema covers 100% of parameters with descriptions, so baseline is 3. The description adds no additional meaning beyond what the schema already provides for 'incident_id'. It merely restates the tool's purpose.

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

Purpose5/5

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

The description 'Acknowledge an open incident' clearly specifies the action (acknowledge) on a resource (incident), distinguishing it from sibling tools like list_open_incidents which list incidents. It is concise and unambiguous.

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, such as when to acknowledge vs. close an incident, or any prerequisites. The agent receives no context for decision-making.

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/cloudbring/newrelic-mcp'

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