Skip to main content
Glama

Change an incident

update_incident
Idempotent

Changes the title status pages show (public_title) or the root cause (Pro plans) of any incident, and the title, severity and monitors of one opened by hand. Fields left out keep their value. 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": "update_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoWhat the dashboard, alerts and status pages call it.
severityNoHow serious the problem is.critical
root_causeNoWhat caused the incident (Pro plans); null clears it.
incident_idYesIncident ID from list_incidents.
monitor_idsNoThe monitors it affects (GET /monitors): its updates show on the published status pages that show any of them. None or up to 50.
public_titleNoThe title status pages show instead of the incident's own; null goes back to its own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / public_title / description
      Added value: +"The title status pages show instead of the incident's own; null goes back to its own."
    • addedInput schema / properties / root_cause / description
      Added value: +"What caused the incident (Pro plans); null clears it."
    • addedInput schema / properties / severity / description
      Added value: +"How serious the problem is."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the safety profile is covered. The description usefully adds PATCH-style semantics ("Fields left out keep their value") and plan gating (root cause requires Pro), but "Free" is a cryptic fragment whose meaning (tier availability vs. no cost) is left to the reader.

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 dense sentences with no filler, and the field-scoping constraint is front-loaded. The single sentence packing three field groups plus a parenthetical plan note parses a bit awkwardly, and the trailing "Free." is too terse to communicate anything reliably.

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 6-parameter mutation with no output schema, the description covers the essentials an agent needs: partial-update behavior, per-field applicability, and plan gating. It stops short of saying what the call returns or what happens when a field is rejected for the given incident type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns one more by attaching conditions to parameters that the schema does not encode, namely that title, severity and monitor_ids only apply to incidents opened by hand while public_title/root_cause apply to any incident.

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 (Changes) and resource (incident) and enumerates the mutable fields, distinguishing them by incident origin: public_title/root_cause for any incident vs title/severity/monitors only for hand-opened ones. That is more specificity than most update tools offer, though it never names a sibling to contrast with.

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 when fields are applicable (which fields work on which kind of incident), which is usable guidance, but it never says when to use this versus post_incident_update, resolve_incident, or acknowledge_incident, nor does it state prerequisites or error behavior for a disallowed field.

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