SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Diagnose check

diagnose_check

Read-onlyIdempotent

Diagnose a single uptime check in one call: get current status, recent regional results, and active or last resolved incidents instead of chaining separate list calls.

Instructions

Return everything an operator would want to look at to diagnose a single check's current state in one call: current status, recent raw results across regions, any active incident, and the most recent resolved incident. Use this instead of chaining list_results + list_incidents when a human asks "what's wrong with check X?". freshness and regionalIssue are omitted when there is nothing to report, the incidents are null when there are none. Read-only: works with mcp:read tokens.

Input Schema

Name	Required	Description	Default
`identifier`	Yes	Check UID or slug (e.g. "api-prod" or a UUID).
`recentResultsLimit`	No	Recent raw results per region (1-20, default 5).

Output Schema

Name	Required	Description
`check`	Yes
`freshness`	No	One sentence per silent region naming it and since when it has gone quiet; empty when every region is reporting.
`recentResults`	Yes	Newest-first raw results, trimmed to recentResultsLimit per region; includes region, output and durationMs.
`regionalIssue`	No	One sentence describing the regional issue (some, but fewer than the quorum, of the check's regions failing); empty when there is none.
`activeIncident`	Yes	Currently-open incident for the check, or null when none is open.
`lastResolvedIncident`	Yes	Most recently resolved incident for the check, or null when there is none.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.42.0Oct 27, 2026
- addedInput schema / properties / identifier / maxLength
```
Added value: +2048
```
- addedInput schema / properties / identifier / minLength
```
Added value: +1
```
Changed3 schema fields changedv0.41.0Oct 23, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / check / additionalProperties
```
Added value: +false
```

Changed1 schema field changedv0.38.5Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activeIncident": {
+      "description": "Currently-open incident for the check, or null when none is open.",
+      "properties": {
+        "checkUid": {
+          "description": "UID of the check the incident belongs to.",
+          "type": "string"
+        },
+        "kind": {
+          "description": "What the incident is about: check, slo_burn or degraded.",
+          "type": "string"
+        },
+        "number": {
+          "description": "Short per-org reference, rendered as #42.",
+          "type": "integer"
+        },
+        "resolvedAt": {
+          "description": "RFC3339 resolution timestamp; absent while the incident is open.",
+          "type": "string"
+        },
+        "startedAt": {
+          "description": "RFC3339 timestamp of the incident's onset.",
+          "type": "string"
+        },
+        "state": {
+          "description": "Incident state, e.g. active or resolved.",
+          "type": "string"
+        },
+        "uid": {
+          "description": "Incident UID.",
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "check": {
+      "properties": {
+        "checkGroupUid": {
+          "description": "Check group UID, when the check belongs to a group.",
+          "type": "string"
+        },
+        "config": {
+          "description": "Check-specific configuration for the type.",
+          "type": "object"
+        },
+        "createdAt": {
+          "description": "RFC3339 creation timestamp.",
+          "type": "string"
+        },
+        "description": {
+          "description": "Free-text description.",
+          "type": "string"
+        },
+        "enabled": {
+          "description": "Whether the check runs.",
+          "type": "boolean"
+        },
+        "labels": {
+          "description": "Key-value labels.",
+          "type": "object"
+        },
+        "lastResultAt": {
+          "description": "RFC3339 timestamp of the newest real result.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Human-readable name.",
+          "type": "string"
+        },
+        "period": {
+          "description": "Check interval as HH:MM:SS.",
+          "type": "string"
+        },
+        "placement": {
+          "description": "\"pinned\" or \"auto\".",
+          "type": "string"
+        },
+        "regions": {
+          "description": "Regions the check runs from.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "slug": {
+          "description": "URL-friendly slug.",
+          "type": "string"
+        },
+        "status": {
+          "description": "Synthesized status: up, down, validating, created or degraded.",
+          "type": "string"
+        },
+        "statusChangedAt": {
+          "description": "RFC3339 timestamp of the last status change.",
+          "type": "string"
+        },
+        "type": {
+          "description": "Check type, e.g. \"http\".",
+          "type": "string"
+        },
+        "uid": {
+          "description": "Check UID.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "uid"
+      ],
+      "type": "object"
+    },
+    "freshness": {
+      "description": "One sentence per silent region naming it and since when it has gone quiet; empty when every region is reporting.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "lastResolvedIncident": {
+      "description": "Most recently resolved incident for the check, or null when there is none.",
+      "properties": {
+        "checkUid": {
+          "description": "UID of the check the incident belongs to.",
+          "type": "string"
+        },
+        "kind": {
+          "description": "What the incident is about: check, slo_burn or degraded.",
+          "type": "string"
+        },
+        "number": {
+          "description": "Short per-org reference, rendered as #42.",
+          "type": "integer"
+        },
+        "resolvedAt": {
+          "description": "RFC3339 resolution timestamp; absent while the incident is open.",
+          "type": "string"
+        },
+        "startedAt": {
+          "description": "RFC3339 timestamp of the incident's onset.",
+          "type": "string"
+        },
+        "state": {
+          "description": "Incident state, e.g. active or resolved.",
+          "type": "string"
+        },
+        "uid": {
+          "description": "Incident UID.",
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "recentResults": {
+      "description": "Newest-first raw results, trimmed to recentResultsLimit per region; includes region, output and durationMs.",
+      "items": {
+        "properties": {
+          "availabilityPct": {
+            "description": "Uptime % for the bucket (with=availabilityPct, aggregated rows only).",
+            "type": "number"
+          },
+          "checkName": {
+            "description": "Check name (with=checkName).",
+            "type": "string"
+          },
+          "checkSlug": {
+            "description": "Check slug (with=checkSlug).",
+            "type": "string"
+          },
+          "checkUid": {
+            "description": "UID of the check this result belongs to.",
+            "type": "string"
+          },
+          "durationMs": {
+            "description": "Response time in ms (with=durationMs).",
+            "type": "number"
+          },
+          "periodStart": {
+            "description": "RFC3339 start of the period (raw: execution time).",
+            "type": "string"
+          },
+          "periodType": {
+            "description": "Aggregation level: raw, hour, day or month.",
+            "type": "string"
+          },
+          "region": {
+            "description": "Region the check ran in (with=region).",
+            "type": "string"
+          },
+          "status": {
+            "description": "Result status: up, down, created, running, abandoned…",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Result UID (time-ordered).",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "regionalIssue": {
+      "description": "One sentence describing the regional issue (some, but fewer than the quorum, of the check's regions failing); empty when there is none.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "check",
+    "recentResults",
+    "activeIncident",
+    "lastResolvedIncident"
+  ],
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.5/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, so the safety profile is covered; the description still adds auth scope ('works with mcp:read tokens') and, more valuably, discloses output-absence semantics (freshness/regionalIssue omitted when empty, incidents null when none). It does not mention cost, latency, or result-volume limits for the multi-region aggregation, which is the one remaining behavioral gap.

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?

Three sentences, each doing distinct work: what is returned, the sibling alternative, and null/omission semantics plus auth. The payload contents are front-loaded before the usage rule.

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?

An output schema exists, so return values need not be re-explained; the description still pre-empts the confusing part of the response (omitted vs null fields) and states the auth tier. For a 2-parameter read aggregation tool, nothing an agent needs 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with identifier's UID-or-slug format and recentResultsLimit's range/default fully documented in the schema, so baseline 3 applies. The description adds nothing about either parameter beyond the implicit notion of targeting one check.

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?

States a specific verb ('diagnose') and resource ('a single check's current state') and enumerates exactly what is aggregated: status, raw results across regions, active incident, most recent resolved incident. It is also distinguishable from siblings list_results and list_incidents, which it explicitly folds together.

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?

Gives an explicit routing rule: 'Use this instead of chaining list_results + list_incidents when a human asks "what's wrong with check X?"'. Both the alternative and the selecting condition are named, leaving nothing to inference.

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