Skip to main content
Glama

Resolve an incident opened by hand

resolve_incident
Idempotent

Resolves an incident opened with open_incident; the contacts it alerted hear so. A message is published as the last update on its status pages. Incidents opened by checks resolve with their checks. Free.

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": "resolve_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional last update for the status pages that show the incident.
incident_idYesIncident ID from list_incidents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / message / description
      Added value: +"Optional last update for the status pages that show the incident."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavioral context beyond annotations: notifying alerted contacts, publishing the message as the final status-page update, the check-opened exclusion, and 'Free' (no cost). Consistent with annotations (idempotent, non-destructive, open-world). Doesn't say whether resolution is reversible or requires the incident to be in a specific 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?

Four short sentences, front-loaded with the core action and its main side effect. 'Free' is terse but on-topic; no filler.

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

Completeness4/5

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

Covers the key unknowns for a mutation tool: who gets notified, what the message does, and the check-opened exclusion. Missing only state requirements/reversibility, which is acceptable given the small two-parameter surface and no output schema.

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 coverage is 100%, so baseline 3 applies. The description clarifies that the optional message becomes the last update on status pages that show the incident, which slightly enriches the schema's wording but adds little beyond it.

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?

Specific verb+resource: 'Resolves an incident opened with open_incident' and states the side effect (contacts hear, message published as last status update). Distinguishes hand-opened from check-opened incidents. Doesn't explicitly contrast with update_incident or post_incident_update siblings, so not a 5.

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

Usage Guidelines3/5

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

Names the originating tool (open_incident) as the precondition and notes that incidents opened by checks resolve with their checks, implying this tool is for hand-opened incidents only. No explicit statements about when to prefer update_incident or post_incident_update instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources