Skip to main content
Glama

Incident: status and deadlines

incident_status
Read-only

Where an incident stands: each notification deadline, hours left or overdue, and the timeline. Omit incident_id for a list of your incidents. Requires the organization API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "incident_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
incident_idNoOne incident; omit to list all

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 establish readOnlyHint=true and openWorldHint=false, and the description adds two things they don't cover: the auth requirement ('Requires the organization API key') and the shape of what comes back (deadlines, hours remaining/overdue, timeline). With no output schema, that return-content summary is genuinely useful; rate limits and list-size/pagination behavior remain undisclosed.

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 tight sentences: the payload is front-loaded, then the mode switch, then the auth prerequisite. Nothing is repeated and every clause earns its place.

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 read tool with annotations carrying the safety profile, the description covers purpose, both call modes, auth, and return content. The only meaningful gap is list behavior (ordering, truncation, pagination) when incident_id is omitted.

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% and the single parameter already carries the description 'One incident; omit to list all', which is essentially the same instruction repeated in the description. It adds no format, ID-source, or filtering semantics beyond the schema, so the baseline 3 applies.

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?

The description states a concrete resource and what it reports: 'Where an incident stands: each notification deadline, hours left or overdue, and the timeline.' Combined with the name, it is clearly the read/inspection counterpart to incident_open/incident_close/incident_update, though it never names a sibling to draw that contrast explicitly.

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?

'Omit incident_id for a list of your incidents' gives explicit guidance for both call modes (single lookup vs. list), which is the main usage decision for this tool. It stops short of any when-not guidance or pointing at an alternative tool for related questions (e.g., closing or updating an incident).

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