Skip to main content
Glama

Get an incident

get_incident
Read-onlyIdempotent

Get an incident by ID, with its impact, status, state, dates and affected monitors.

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": {
      "project_id": "<project_id>",
      "incident_id": "<incident_id>"
    },
    "name": "get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project to act on, see whoami
incident_idYesID of the incident to show

Output Schema

NameRequiredDescriptionDefault
idNo
slugNoIncident unique slug name
tagsNoResource tags, made of lowercase letters, numbers, `.`, `_`, `:` and `-`. An organization can have up to 200 tags.
typeNoIncident type
stateNoIncident state
titleNoIncident title
impactNoIncident impact
statusNoIncident status
monitorsNoList of monitors linked to the incident
created_atNoDate of creation for the entity
project_idNoParent project ID
updated_atNoDate of last update for the entity
descriptionNoDescription of the error that caused the incident
incident_atNoDate of incident confirmation, defaults to the current date on creation. Must be within the last year and no more than 10 minutes in the future.
recovery_atNoDate of incident recovery. Must be after `incident_at`, within the last year and no more than 10 minutes in the future. Cannot be removed once the incident is recovered.
exclude_from_downtimeNoFlag to exclude the incident from downtime calculations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "created_at": {
      +      "description": "Date of creation for the entity",
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "Description of the error that caused the incident",
      +      "examples": [
      +        "The server answered with an unexpected status code: 503."
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "exclude_from_downtime": {
      +      "description": "Flag to exclude the incident from downtime calculations",
      +      "examples": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "examples": [
      +        1
      +      ],
      +      "type": "integer"
      +    },
      +    "impact": {
      +      "description": "Incident impact",
      +      "enum": [
      +        "unknown",
      +        "operational",
      +        "maintenance",
      +        "degraded_performance",
      +        "partial_outage",
      +        "major_outage"
      +      ],
      +      "type": "string"
      +    },
      +    "incident_at": {
      +      "description": "Date of incident confirmation, defaults to the current date on creation. Must be within the last year and no more than 10 minutes in the future.",
      +      "format": "date-time",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "monitors": {
      +      "description": "List of monitors linked to the incident",
      +      "examples": [
      +        [
      +          1,
      +          2,
      +          3
      +        ]
      +      ],
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    "project_id": {
      +      "description": "Parent project ID",
      +      "examples": [
      +        1
      +      ],
      +      "type": "integer"
      +    },
      +    "recovery_at": {
      +      "description": "Date of incident recovery. Must be after `incident_at`, within the last year and no more than 10 minutes in the future. Cannot be removed once the incident is recovered.",
      +      "format": "date-time",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "slug": {
      +      "description": "Incident unique slug name",
      +      "examples": [
      +        "APP-123"
      +      ],
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "Incident state",
      +      "enum": [
      +        "unknown",
      +        "investigating",
      +        "identified",
      +        "monitoring",
      +        "resolved"
      +      ],
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Incident status",
      +      "enum": [
      +        "ongoing",
      +        "recovering",
      +        "recovered"
      +      ],
      +      "type": "string"
      +    },
      +    "tags": {
      +      "description": "Resource tags, made of lowercase letters, numbers, `.`, `_`, `:` and `-`. An organization can have up to 200 tags.",
      +      "items": {
      +        "examples": [
      +          "environment:production"
      +        ],
      +        "type": "string"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "title": {
      +      "description": "Incident title",
      +      "examples": [
      +        "Service is not working as expected"
      +      ],
      +      "type": "string"
      +    },
      +    "type": {
      +      "description": "Incident type",
      +      "enum": [
      +        "monitor",
      +        "manual"
      +      ],
      +      "type": "string"
      +    },
      +    "updated_at": {
      +      "description": "Date of last update for the entity",
      +      "format": "date-time",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive operation, which covers the safety profile. The description adds a brief summary of returned incident details, but says nothing about missing-incident behavior, permissions, or rate limits. With the annotations carrying most of the behavioral burden, this is adequate but not rich.

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?

The definition is a single front-loaded sentence with no filler. The resource and lookup key appear immediately, followed by a compact list of returned fields.

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 simple two-parameter read tool with full schema coverage, annotations, and an output schema, the description is nearly complete. It does not mention error behavior for an invalid incident ID, but that is a minor omission for correct invocation.

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 description coverage is 100%, and both required parameters are documented in the input schema. The description says 'by ID' but adds no format, range, or relationship details beyond the schema. This matches the baseline when the schema fully documents the parameters.

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 uses a specific verb and resource: get an incident by ID. It also lists the returned details (impact, status, state, dates, affected monitors). It does not explicitly distinguish itself from siblings such as list_incidents, though the 'by ID' scope implies the difference.

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 phrase 'by ID' implies this tool is used when a specific incident identifier is known. However, it does not explicitly say when to prefer this over list_incidents or how it relates to update_incident and recover_incident. Usage is therefore only indirectly conveyed.

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