Skip to main content
Glama

mark_incident

Change an incident's state to open, on it, or resolved and return the updated incident so teams can track who is working on it and what is finished.

Instructions

Change where an incident stands. incident is its id, as what_is_broken shows it. state is on_it (you or the person is working on it), resolved (it is over) or open (nobody is on it and it is not over). It is recorded under the key the caller uses, so a read-only key is refused and the answer says so. So is a change the incident's state does not allow: a resolved incident cannot go to on_it until it is open again. Returns the incident as it stands now.

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": "<incident>",
      "state": "<state>"
    },
    "name": "mark_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
incidentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, yet the description covers the important behavioral traits itself: a write that requires a non-read-only key, state-machine restrictions on allowed transitions, and error surfaces that report the refusal. It does not address idempotency or what happens if the state is already the requested value, which keeps it from a 5.

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?

Front-loaded with the action, then parameter meanings, then failure modes, then the return value. Dense and mostly waste-free, though sentences are long and slightly run-on, and a bulleted state list would scan faster than inline prose.

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 two-parameter mutation tool with an output schema, everything an agent needs is present: what the tool does, valid state vocabulary, authorization requirement, transition legality, and error reporting. Return values are covered by the output schema, and the one-line note about returning the incident is a useful confirmation rather than filler.

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

Parameters5/5

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

Schema description coverage is 0% and `state` is a bare string with no enum, so the description carries the full burden and does: it defines all three values (on_it, resolved, open) in operational terms and explains that `incident` is the id as surfaced by `what_is_broken`. This is meaning added beyond the schema, not restatement.

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 opens with a specific verb+resource ('Change where an incident stands') and immediately disambiguates the two parameters, including enumerating the three valid states with plain-language meanings. It also anchors `incident` to the sibling tool `what_is_broken`, so an agent can locate valid ids without opening another 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?

It states the conditions under which a call fails: a read-only key is refused, and a transition the incident's current state forbids (resolved -> on_it without reopening) is rejected. That is clear context for correct invocation, though it stops short of naming any alternative tool for cases where marking is the wrong action.

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