Opsphere — DevOps & SRE Intelligence

Get a single Pingdom check

pingdom_check_get

Read-only

Returns full details of a single Pingdom check by ID: hostname, type, current status, last test time, last error time, resolution, tags, contacts. Optionally expands the last 3 raw results (expandResults: true) to include root-cause messages.

Input Schema

Name	Required	Description
`checkId`	Yes	Numeric Pingdom check ID (string is coerced to number)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`expandResults`	No	If true, fetch the last 3 raw results and include them in the response

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- addedOutput schema / properties / data / properties / records / items / properties / checkId
```
Added value: +{
+  "type": "number"
+}
```

Changed26 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

removedOutput schema / properties / data / properties / data

Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/properties/data/properties/items"
-    },
-    {
-      "$ref": "#/properties/data/properties/items/items"
-    }
-  ]
-}

removedOutput schema / properties / data / properties / error

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "$ref": "#/properties/data/properties/items/items"
-    }
-  ]
-}

addedOutput schema / properties / data / properties / family

Added value: +{
+  "const": "pingdom",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / message
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / data / properties / meta

Removed value: -{
-  "$ref": "#/properties/data/properties/items/items"
-}

removedOutput schema / properties / data / properties / nextCursor

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / data / properties / ok
```
Removed value: -{
-  "type": "boolean"
-}
```

addedOutput schema / properties / data / properties / operation

Added value: +{
+  "const": "pingdom_check_get",
+  "type": "string"
+}

removedOutput schema / properties / data / properties / pageInfo

Removed value: -{
-  "$ref": "#/properties/data/properties/items/items"
-}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / records

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "createdAt": {
+        "type": "string"
+      },
+      "environment": {
+        "type": "string"
+      },
+      "facts": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "value": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                },
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "number",
+                      "boolean",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                }
+              ]
+            }
+          },
+          "required": [
+            "name",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "hostname": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "metric": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "responseTimeMs": {
+        "type": "number"
+      },
+      "severity": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "timestamp": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "unit": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "type": "string"
+      },
+      "uptimePercent": {
+        "type": "number"
+      },
+      "url": {
+        "type": "string"
+      },
+      "value": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "facts"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / results

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / status

Removed value: -{
-  "type": [
-    "string",
-    "number"
-  ]
-}

addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / text
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / data / properties / total / minimum
```
Added value: +0
```
changedOutput schema / properties / data / properties / total / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "family",
+  "operation",
+  "records",
+  "total",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it lists exactly what state is returned and explains that expandResults pulls the last 3 raw results, which carry root-cause messages — a cost/benefit hint the schema only partially conveys.

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?

Two tight clauses, front-loaded with the resource and lookup key, followed by the optional expansion behavior. Every phrase maps to a field or parameter; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With read-only annotations, full schema coverage, and an output schema, the description covers everything needed to call the tool correctly. Only minor omissions remain (behavior on unknown checkId, when the optional context_id matters), which the surrounding tooling likely handles.

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 the baseline is 3. The description confirms checkId is the lookup key and reframes expandResults as fetching root-cause messages, but it says nothing about context_id or about what omitting context_id implies, leaving the schema to carry the rest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns full details of a single Pingdom check by ID') and enumerates the returned fields (hostname, type, status, last test/error time, resolution, tags, contacts). It implicitly distinguishes itself from pingdom_check_outages and pingdom_check_probes_status by scope ('single check'), but does not name those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it already has a checkId and needs full configuration/state details. There is no explicit guidance on when to prefer this over pingdom_check_outages, pingdom_check_probes_status, or pingdom_actions_recent, nor any stated prerequisite for obtaining the ID.

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

All Opsphere — DevOps & SRE Intelligence 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.

Resources

Need Help?