SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Get incident

get_incident

Read-onlyIdempotent

Fetch one incident by UID to view its state, timestamps, failure counts, timeline events, and optional notification attempts.

Instructions

Get a single incident by UID; an unknown UID fails with an "incident not found" error. Returns the incident object — number, state, timestamps, failure counts — plus the check with with=check and up to 50 timeline events with with=events. include=["notifications"] adds the incident's notification attempts (one row per dispatch target with its delivery status, channel and recipient, newest first), filtered by status and capped by limit. Use list_incidents to search and filter across incidents, and diagnose_check for a check's full triage briefing. Read-only: works with mcp:read tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`uid`	Yes	Incident UID returned by list_incidents or diagnose_check.
`with`	No	Comma-separated extra fields. "check" includes the underlying check; "events" includes up to 50 most-recent timeline events (status transitions, notifications, manual notes). Example: "check,events".
`limit`	No	With include=notifications: max attempts (1-500, default 20).
`status`	No	With include=notifications: only attempts in this delivery status. Allowed: pending, sent, failed, cancelled, skipped.
`include`	No	Extra lists to return with the incident. An unknown value is an error.

Output Schema

TableJSON Schema

Name	Required	Description
`uid`	Yes	Incident UID.
`kind`	No	What the incident is about: check, slo_burn or degraded.
`check`	No	Underlying check, when requested with with=check.
`state`	No	active or resolved.
`title`	No	Custom title, when one was set.
`events`	No	Timeline events (status transitions, notifications, manual notes), newest first; present when with=events was passed.
`number`	No	Short per-org reference, e.g. 42.
`checkUid`	No	UID of the check the incident is about.
`checkName`	No	Name of that check.
`checkSlug`	No	Slug of that check.
`startedAt`	No	RFC3339 timestamp when the incident opened.
`resolvedAt`	No	RFC3339 timestamp when it resolved; absent while active.
`description`	No	Custom description, when one was set.
`failureCount`	No	Number of failures recorded for the incident.
`relapseCount`	No	Number of times the incident reopened.
`notifications`	No	Notification attempts, newest first; present when include=notifications was passed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.38.5Oct 15, 2026

addedInput schema / properties / include

Added value: +{
+  "description": "Extra lists to return with the incident. An unknown value is an error.",
+  "items": {
+    "enum": [
+      "notifications"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "With include=notifications: max attempts (1-500, default 20).",
+  "type": "integer"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "With include=notifications: only attempts in this delivery status. Allowed: pending, sent, failed, cancelled, skipped.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "check": {
+      "description": "Underlying check, when requested with with=check.",
+      "type": "object"
+    },
+    "checkName": {
+      "description": "Name of that check.",
+      "type": "string"
+    },
+    "checkSlug": {
+      "description": "Slug of that check.",
+      "type": "string"
+    },
+    "checkUid": {
+      "description": "UID of the check the incident is about.",
+      "type": "string"
+    },
+    "description": {
+      "description": "Custom description, when one was set.",
+      "type": "string"
+    },
+    "events": {
+      "description": "Timeline events (status transitions, notifications, manual notes), newest first; present when with=events was passed.",
+      "items": {
+        "properties": {
+          "actorName": {
+            "description": "Display name of the acting user, when known.",
+            "type": "string"
+          },
+          "actorType": {
+            "description": "Who acted: system or user.",
+            "type": "string"
+          },
+          "createdAt": {
+            "description": "RFC3339 timestamp of the event.",
+            "type": "string"
+          },
+          "eventType": {
+            "description": "Event type, e.g. \"incident.created\".",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Event UID.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "failureCount": {
+      "description": "Number of failures recorded for the incident.",
+      "type": "integer"
+    },
+    "kind": {
+      "description": "What the incident is about: check, slo_burn or degraded.",
+      "type": "string"
+    },
+    "notifications": {
+      "description": "Notification attempts, newest first; present when include=notifications was passed.",
+      "items": {
+        "properties": {
+          "channelType": {
+            "description": "Delivery channel, e.g. email or slack.",
+            "type": "string"
+          },
+          "connection": {
+            "description": "Targeted integration {uid, name, type}, or null when the target was a user.",
+            "properties": {
+              "name": {
+                "description": "Integration name.",
+                "type": "string"
+              },
+              "type": {
+                "description": "Integration type, e.g. email or webhook.",
+                "type": "string"
+              },
+              "uid": {
+                "description": "Integration UID.",
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "createdAt": {
+            "description": "RFC3339 timestamp when the attempt was recorded.",
+            "type": "string"
+          },
+          "error": {
+            "description": "Delivery error; absent when there was none.",
+            "type": "string"
+          },
+          "eventType": {
+            "description": "Incident event that triggered the attempt.",
+            "type": "string"
+          },
+          "incident": {
+            "description": "Incident context {uid, title, state, startedAt}; absent unless the query filled it.",
+            "properties": {
+              "startedAt": {
+                "description": "RFC3339 incident start.",
+                "type": "string"
+              },
+              "state": {
+                "description": "Incident state: active or resolved.",
+                "type": "string"
+              },
+              "title": {
+                "description": "Incident title.",
+                "type": "string"
+              },
+              "uid": {
+                "description": "Incident UID.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "incidentUid": {
+            "description": "Incident the attempt belongs to.",
+            "type": "string"
+          },
+          "messageId": {
+            "description": "Provider message ID; absent when the channel did not return one.",
+            "type": "string"
+          },
+          "repeatIndex": {
+            "description": "Escalation repeat round; absent for direct sends.",
+            "type": "integer"
+          },
+          "sentAt": {
+            "description": "RFC3339 timestamp when it was delivered; absent until sent.",
+            "type": "string"
+          },
+          "skipReason": {
+            "description": "Why the attempt was skipped; absent when it was not skipped.",
+            "type": "string"
+          },
+          "source": {
+            "description": "What triggered it, e.g. check_connection, escalation_user or escalation_schedule.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Delivery status: pending, sent, failed, cancelled or skipped.",
+            "type": "string"
+          },
+          "stepUid": {
+            "description": "Escalation step that produced the attempt; absent for direct sends.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Notification row UID.",
+            "type": "string"
+          },
+          "user": {
+            "description": "Targeted user {uid, name}, or null when the target was a connection.",
+            "properties": {
+              "name": {
+                "description": "User display name.",
+                "type": "string"
+              },
+              "uid": {
+                "description": "User UID.",
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "number": {
+      "description": "Short per-org reference, e.g. 42.",
+      "type": "integer"
+    },
+    "relapseCount": {
+      "description": "Number of times the incident reopened.",
+      "type": "integer"
+    },
+    "resolvedAt": {
+      "description": "RFC3339 timestamp when it resolved; absent while active.",
+      "type": "string"
+    },
+    "startedAt": {
+      "description": "RFC3339 timestamp when the incident opened.",
+      "type": "string"
+    },
+    "state": {
+      "description": "active or resolved.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Custom title, when one was set.",
+      "type": "string"
+    },
+    "uid": {
+      "description": "Incident UID.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "uid"
+  ],
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real behavioral context: unknown UIDs produce an 'incident not found' error, notifications are returned newest-first one row per dispatch target, and read access requires mcp:read tokens. It stops short of describing pagination or truncation behavior for timeline events beyond the 50 cap.

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 core operation, then qualification, then alternatives. The middle sentence is long and packs several clauses, but nearly every clause carries information an agent needs; little is filler.

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?

Given an output schema already exists, the description need not explain return shapes, yet it still summarizes returns (number, state, timestamps, failure counts) and covers error behavior, auth scope, and the interaction among with/include/status/limit. Nothing needed to call it correctly is missing.

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, but the description adds relational meaning the schema states only per-field: it explains that with=check/with=events are opt-in extras, that include=["notifications"] is filtered by status and capped by limit, and that events are capped at 50 most-recent. This ties the parameters together rather than restating them.

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?

Opens with a specific verb+resource and scope: 'Get a single incident by UID'. It immediately distinguishes itself from the sibling list_incidents ('Use list_incidents to search and filter across incidents') and names the exact identifier type the tool consumes.

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?

Explicitly routes the agent to alternatives with conditions: list_incidents for search/filter over many incidents, diagnose_check for a check's triage briefing. It also states the failure mode for an unknown UID, so the agent knows what to expect when guessing a UID.

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