Skip to main content
Glama
fclairamb

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Diagnose check

diagnose_check
Read-onlyIdempotent

Diagnose a single check's current state in one call: status, recent regional results, active incident, and last resolved incident. Read-only; replaces chaining list_results and list_incidents.

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?". Returns {check, freshness, regionalIssue, recentResults, activeIncident, lastResolvedIncident} — 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

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesCheck UID or slug (e.g. "api-prod" or a UUID).
recentResultsLimitNoRecent raw results per region (1-20, default 5).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkYes
freshnessNoOne sentence per silent region naming it and since when it has gone quiet; empty when every region is reporting.
recentResultsYesNewest-first raw results, trimmed to recentResultsLimit per region; includes region, output and durationMs.
regionalIssueNoOne sentence describing the regional issue (some, but fewer than the quorum, of the check's regions failing); empty when there is none.
activeIncidentYesCurrently-open incident for the check, or null when none is open.
lastResolvedIncidentYesMost recently resolved incident for the check, or null when there is none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.38.5
    • 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"
+}
  2. First observedv0.32.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds genuinely new context: the return envelope keys, that freshness and regionalIssue are omitted when empty and incidents are null when none exist, and the auth requirement ('works with mcp:read tokens'). That is exactly the kind of behavioral detail annotations cannot express.

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 purpose, then the usage rule, then the return shape and auth note in a logical order. The return-shape sentence is dense with parenthetical qualifiers, slightly overlong, but every sentence carries distinct information with no 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?

An output schema exists, so the description is not obligated to explain return values, yet it briefly summarizes the envelope and its omission semantics. Combined with the usage rule and auth note, an agent has everything needed to invoke this correctly on the first try.

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%, so identifier (UID or slug) and recentResultsLimit (1-20, default 5) are already fully documented in the schema. The description references 'check X' generically and adds no format, default, or constraint detail beyond what the schema provides, 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?

States a specific verb (diagnose) plus resource (a single check) and enumerates exactly what it aggregates: current status, recent raw results across regions, active incident, and last resolved incident. It explicitly distinguishes itself from the aggregation siblings list_results + list_incidents, so an agent can separate it from the many list_*/get_* tools without opening a 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?

Gives an explicit when-to-use rule ('when a human asks "what's wrong with check X?"') and names the alternative it replaces (chaining list_results + list_incidents). The selection condition is unambiguous.

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