Opsphere — DevOps & SRE Intelligence

Pingdom recent actions and alerts

pingdom_actions_recent

Read-only

Returns the most recent Pingdom actions and notifications (state changes and alerts fired) over a configurable time window. Use this to correlate "did Pingdom alert when we expected?" or to audit which checks triggered notifications. Optionally scope to a specific checkId or filter by action type.

Input Schema

Name	Required	Description
`hours`	No	Time window in hours (default 24, max 168)
`limit`	No	Max actions to return (default 50, max 200)
`typeIn`	No	Optional: filter by action type
`checkId`	No	Optional: scope to a specific check ID
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

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_actions_recent",
+  "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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: the records are state changes and fired alerts over a configurable window, which is what an agent needs to interpret results. It omits truncation behavior (limit default/max) though that is visible in the schema.

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, front-loaded with what is returned, followed by use cases and filtering options. No filler or repeated information.

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 an output schema present and annotations covering safety, the description supplies enough for correct invocation: scope, window concept, and filters. The only small gap is that defaults (24h, 50 results) and result-cap semantics are left entirely to the schema.

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% and the schema already documents hours, limit, typeIn, checkId, and context_id with defaults and bounds. The description's mention of a configurable time window, checkId scoping, and action-type filtering largely restates the schema, adding intent but no new syntax or constraints.

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 and resource: returns recent Pingdom actions and notifications (state changes and alerts fired). It also names the time-window scoping and optional checkId/type filters, which separates it from siblings like pingdom_check_outages (availability gaps) and pingdom_check_get (config lookup).

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

Usage Guidelines4/5

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

Gives concrete situations to use it: correlating whether Pingdom alerted when expected, and auditing which checks triggered notifications. It does not explicitly name the alternative tool (e.g., pingdom_check_outages) or state when to prefer that sibling, so it stops short of a 5.

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?