SolidPing

Get incident

get_incident

Read-onlyIdempotent

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

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

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.

First observedNov 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent, yet the description adds auth detail ('works with mcp:read tokens'), failure behavior ('unknown UID fails with an "incident not found" error'), event cap (50 most-recent), and notification ordering ('newest first') plus that an unknown include value is an error.

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 action and error case, then option behavior, then routing. It is dense — clauses like 'plus the check with with=check and up to 50 timeline events with with=events' stack qualifiers — but almost nothing is redundant.

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?

Even though an output schema exists, the description tells the agent which optional data appears in the response and what can fail, which is everything needed to call it correctly on the first try.

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 baseline is 3; the description goes beyond it by explaining the shape of the notifications list (one row per dispatch target with delivery status, channel and recipient, newest first) and how status/limit interact with include=notifications.

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 precise verb+resource and scope: 'Get a single incident by UID'. It immediately separates itself from list_incidents (search/filter) and diagnose_check (check triage), so an agent can choose 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 search and filter across incidents, and diagnose_check for a check's full triage briefing.' It also states the condition that selects this tool (known single UID) versus those alternatives.

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

All SolidPing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.