Opsphere — DevOps & SRE Intelligence

PagerDuty incident detail

pd_incident_get

Read-only

Get a single incident by ID. Optional include[] for related objects.

Input Schema

Name	Required	Description
`id`	Yes	Incident ID (e.g. PXXXXXX)
`include`	No	Related objects to embed (e.g. services, assignees, escalation_policies)
`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.

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": "pagerduty",
+  "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": "pd_incident_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": {
+      "assignee": {
+        "type": "string"
+      },
+      "body": {
+        "type": "string"
+      },
+      "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"
+      },
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "priority": {
+        "type": "string"
+      },
+      "project": {
+        "type": "string"
+      },
+      "reporter": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "type": "string"
+      },
+      "urgency": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered by structured data. The description's only added behavioral detail is that related objects can be embedded via include[], which is closer to parameter semantics than behavior; nothing is said about rate limits, error cases, or ID format expectations.

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?

Two short sentences with the core action front-loaded and no filler. It is arguably under-specified rather than overwritten, but every sentence earns its place.

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?

The tool has full schema coverage, an output schema (so return values need no explanation), and read-only annotations that carry the risk profile. For a simple single-resource fetch, what is missing is only the routing hint toward pd_incidents_search, which is a minor gap rather than a blocking one.

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 all three parameters are documented in the schema, including include[] examples (services, assignees, escalation_policies) and the optional context_id. The description's note about include[] duplicates rather than extends the schema, so baseline 3 applies.

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: 'Get a single incident by ID'. Combined with the title, an agent knows this fetches one PagerDuty incident, and 'single' implicitly distinguishes it from pd_incidents_search. However, it never names the sibling search tool, so the differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, no prerequisite such as 'requires an incident ID obtained from pd_incidents_search', and no exclusion. The only hint is that an ID is required, which an agent must infer from the wording.

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?