Skip to main content
Glama

incident_resolve

Resolve an incident by ID to clear its error state and let the related process continue or be retried; applies only to custom incident types.

Instructions

Resolve an incident by ID, clearing the error state and allowing the process to continue or be retried. Only applicable to custom incident types.

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": {
      "id": "<id>"
    },
    "name": "incident_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the concrete effect of the call (error state cleared, execution resumes or can be retried), which is real behavioral value, but omits idempotency, required permissions, what happens if the incident is not a custom type, and failure behavior.

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?

Two sentences, front-loaded with the action and effect, with the applicability caveat following. No redundant or filler wording; slightly denser parameter guidance could be added without bloat.

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?

For a one-parameter, non-destructive-looking operation with no output schema, the description covers purpose, effect, and a scoping restriction. The remaining gap is return/error semantics, which is minor at this complexity level.

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 has a single required 'id' string with zero description coverage. The phrase 'by ID' confirms the identifier selects the incident but adds no format, source, or origin detail (e.g. whether the ID comes from incident_list or incident_getById) beyond what the schema already shows.

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?

States a specific verb and resource ('Resolve an incident by ID') and spells out the effect: clearing the error state so the process can continue or be retried. It is clear enough to distinguish from read-oriented siblings like incident_getById, though it never names them explicitly.

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 clause 'Only applicable to custom incident types' is a genuine when-not constraint, which is more than most definitions offer. However, there is no guidance on when to reach for this versus adjacent tools such as task_resolve or what to do for non-custom incident types, leaving the agent to infer the alternative path.

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

Deploy Server

Other Tools