SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Get check

get_check

Read-onlyIdempotent

Retrieve metadata for one uptime check using its UID or slug; optionally include the last result and last status change.

Instructions

Get a single check's metadata by UID or slug (identifier takes either); ask for extras with with=lastResult,lastStatusChange. For a full triage briefing (current status + recent results + active incidents), prefer diagnose_check; to search by name or label, use list_checks. Read-only: works with mcp:read tokens.

Input Schema

Name	Required	Description	Default
`with`	No	Comma-separated extra fields: lastResult — most recent result lastStatusChange — when status last changed Example: "lastResult,lastStatusChange".
`identifier`	Yes	Check UID or URL-friendly slug, e.g. "api-prod" or "63d49e55-97e3-4e8c-b7ab-c862de7a43f3".

Output Schema

Name	Required	Description
`uid`	Yes	Check UID.
`name`	No	Human-readable name.
`slug`	No	URL-friendly slug.
`type`	No	Check type, e.g. "http".
`config`	No	Check-specific configuration for the type.
`labels`	No	Key-value labels.
`period`	No	Check interval as HH:MM:SS.
`status`	No	Synthesized status: up, down, validating, created or degraded.
`enabled`	No	Whether the check runs.
`regions`	No	Regions the check runs from.
`createdAt`	No	RFC3339 creation timestamp.
`placement`	No	"pinned" or "auto".
`description`	No	Free-text description.
`lastResultAt`	No	RFC3339 timestamp of the newest real result.
`checkGroupUid`	No	Check group UID, when the check belongs to a group.
`statusChangedAt`	No	RFC3339 timestamp of the last status change.

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedv0.38.5Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

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/non-destructive, and the description reinforces this with auth-level detail the annotations cannot express: it works with mcp:read tokens. It also discloses the opt-in 'extras' expansion behavior, though it does not describe payload shape or size limits.

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?

One dense, front-loaded sentence chain with zero filler: core purpose first, then extras, then alternative routing, then the auth note. Every clause carries information an agent needs.

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 no explanation, annotations cover the safety profile, and both parameters are fully documented. Combined with explicit sibling routing, nothing an agent needs to invoke 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 coverage is 100% and both parameters carry detailed descriptions, including the enum-like list of allowed 'with' values. The description's 'identifier takes either' and its 'with=lastResult,lastStatusChange' example largely restate the schema, so it adds little semantic value beyond it.

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?

Specific verb and resource ('Get a single check's metadata') plus an explicit identifier scope ('by UID or slug'). It names the two siblings it is not (diagnose_check, list_checks), so an agent can select it without opening another 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 diagnose_check for a full triage briefing and list_checks to search by name or label. Both alternatives come with the condition that selects them, 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.