Skip to main content
Glama

Incident: close and seal the report

incident_close

Close an incident and get a sealed post-incident report (timeline, deadlines met or missed, root cause) whose SHA-256 is anchored on chain, ready for customers, insurers or regulators. Requires the organization API key.

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>",
      "root_cause": "<root_cause>",
      "actor": "<actor>"
    },
    "name": "incident_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesWho is doing this (person or agent)
root_causeYesRoot cause and fix
incident_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as non-read-only, non-destructive, non-idempotent, and open-world, so the safety bar is partly covered. The description adds real behavioral context the annotations can't convey: the operation produces an immutable, cryptographically sealed artifact anchored on chain, and it requires an org-scoped API key. It stops short of saying whether closing is terminal or what happens on a repeat call, which matters given idempotentHint=false.

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?

Two sentences, both front-loaded and dense with decision-relevant content: the action first, then the artifact and its guarantees, then the auth prerequisite. The parenthetical enumerating report contents earns its space by defining the output, and there is 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?

With no output schema, the description usefully compensates by enumerating what the sealed report contains and how it is anchored. For a three-required-parameter mutation, the main remaining gap is lifecycle behavior: whether closing is reversible, whether re-closing errors, and what the caller should expect to do with the returned seal.

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 67%, with incident_id carrying no description in the schema and getting no explanation here either. The description mentions root cause only as part of the report output, not as an input the caller must supply, and says nothing about the 'actor' field's role in the sealed record. Adequate baseline given partial schema coverage, but no compensating detail.

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?

Names a specific verb and resource ('Close an incident') and immediately states the deliverable: a sealed post-incident report with timeline, deadline status, root cause, and an on-chain SHA-256 anchor. That outcome profile makes it unmistakable against siblings like incident_update or incident_status without needing to name them.

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?

The description implies the context of use ('ready for customers, insurers or regulators') and states the prerequisite ('Requires the organization API key'), which is genuinely useful. It gives no explicit when-not guidance, no mention of what to do if the incident is already closed, and doesn't route to incident_update for partial changes.

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