Skip to main content
Glama
Sign In
OpenUptime

OpenUptime

by becoolme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_incident

Read-onlyIdempotent

Retrieve a specific incident by UUID to view its write-up, update timeline, related monitors and checks, assignee, and notification deliveries for investigation.

Instructions

Investigate one incident by its UUID from list_incidents. Returns its write-up, update timeline (including internal updates), related monitor/checks, assignee and notification deliveries. Use list_incidents to discover ids; use update_incident to edit the write-up and post_incident_update to change status. This is private team information, unlike list_public_status_page_incidents.

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": "get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource UUID returned by the matching list tool; not its name, incident number or status-page slug.
projectNoProject id (from list_workspaces). Omit to use the default project of the workspace.
workspaceNoWorkspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Resource id (uuid)"New value: +"Resource UUID returned by the matching list tool; not its name, incident number or status-page slug."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds real value beyond them by enumerating what the response contains (write-up, update timeline including internal updates, related monitor/checks, assignee, notification deliveries) and flagging that the data is private team information. It does not mention payload size, pagination, or behavior for missing/archived incidents, 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?

Three front-loaded sentences, the return contents before the routing guidance, no filler. Minor redundancy between 'by its UUID from list_incidents' and 'Use list_incidents to discover ids', which is the only thing keeping it from a 5.

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?

There is no output schema, so the description carries the return-value burden itself and does so concretely (write-up, timeline with internal updates, monitor/checks, assignee, deliveries). Combined with annotations covering the safety profile and a fully documented schema, an agent has everything needed to call it correctly.

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 schema already spells out the UUID format and the 'not a name/incident number/slug' caveat, so the description's 'by its UUID from list_incidents' is largely reinforcement. It adds no extra semantics for the project/workspace parameters, so the baseline 3 applies.

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?

Names a specific verb and resource ('Investigate one incident by its UUID') and immediately scopes it against siblings: list_incidents for discovery, update_incident/post_incident_update for mutation, and list_public_status_page_incidents for the public variant. An agent can pick this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: use list_incidents to discover ids, update_incident to edit the write-up, post_incident_update to change status, and this tool only for private/team incidents rather than public status-page ones. Both the when-to-use and the when-not-to-use cases are stated.

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