Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

Acknowledge an incident

acknowledge_incident
Idempotent

Marks an open incident as acknowledged by you: it stops repeat alerts and tells the team someone is on it (also in PagerDuty). Undo with unacknowledge_incident. Ask the person before calling it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "incident_id": "<incident_id>"
    },
    "name": "acknowledge_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
incident_idYesThe incident id, from status_overview or list_incidents.
organization_idNoThe organization. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare that this is not read-only, is idempotent, and is non-destructive. The description adds useful behavioral detail beyond that: it stops repeat alerts, notifies the team, is reflected in PagerDuty, and can be undone. It does not cover auth requirements or rate limits, but the side effects and reversibility are clearly disclosed.

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 three tight sentences with the core action front-loaded, followed by effects, undo path, and a caution. Every sentence contributes useful selection or invocation context without waste.

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

Completeness5/5

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

For a simple two-parameter action with full schema coverage, rich annotations, and no output schema, the description covers purpose, side effects, reversibility, and a usage caution. Nothing essential for correct selection or invocation is missing.

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 both incident_id and organization_id are already documented in the input schema. The description does not add syntax, format, or additional parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Marks an open incident as acknowledged by you.' It also distinguishes the operation from its inverse by naming unacknowledge_incident, so an agent can identify the intended tool without opening the schema.

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

Usage Guidelines4/5

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

The description gives clear usage context by naming unacknowledge_incident as the undo path and adding the caution 'Ask the person before calling it.' It does not spell out prerequisites or explicit when-not conditions beyond the undo alternative, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InfraNest toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources