Patch MCP

get_agent_test

Read-onlyIdempotent

Read a synthetic test’s status, transcript, result and transcript expiry.

Input Schema

Name	Required	Description	Default
`test_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "error": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "message": {
-        "type": "string"
-      },
-      "next_action": {
-        "type": "string"
-      },
-      "operation_id": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "operation_id",
-      "status"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "createdAt": {
+        "type": "string"
+      },
+      "direction": {
+        "enum": [
+          "inbound",
+          "outbound"
+        ],
+        "type": "string"
+      },
+      "endedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "operation_id": {
+        "type": "string"
+      },
+      "result": {},
+      "revision": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "scenario": {
+        "enum": [
+          "delivery",
+          "reservation",
+          "copay",
+          "custom"
+        ],
+        "type": "string"
+      },
+      "simulatedMessage": {},
+      "startedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "state": {
+        "enum": [
+          "starting",
+          "running",
+          "completed",
+          "stopped",
+          "failed",
+          "timeout",
+          "interrupted"
+        ],
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "transcript": {
+        "items": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "transcriptExpired": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "id",
+      "state",
+      "scenario",
+      "direction",
+      "revision",
+      "title",
+      "startedAt",
+      "createdAt",
+      "endedAt",
+      "transcriptExpired",
+      "transcript",
+      "result",
+      "simulatedMessage"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "error": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "message": {
+        "type": "string"
+      },
+      "next_action": {
+        "type": "string"
+      },
+      "operation_id": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "operation_id",
+      "status"
+    ],
+    "type": "object"
+  }
+]

AddedOct 29, 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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely behavioral detail — that transcripts expire — which hints at urgency in retrieval, but says nothing about what happens when a test is still running or the transcript is unavailable.

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?

One short sentence, front-loaded with the verb and with zero redundant words. It is efficient, though its terseness leaves the gaps noted in the other dimensions rather than resolving them.

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

Completeness3/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 not be explained, and annotations cover the safety profile. Still, the sole required parameter is undocumented and there is no mention of behavior for in-progress tests or expired transcripts — the main failure modes for a test-status read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions test_id, its format, where it comes from, or its length constraints. With a single required parameter the name is semi-self-documenting, but the description contributes nothing beyond the schema.

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 (Read) and resource (a synthetic test) plus the exact payload returned: status, transcript, result, and transcript expiry. That distinguishes it from start_agent_test/stop_agent_test, though it never names the related get_agent_test_listener or explains the difference.

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 can infer this is the polling/retrieval counterpart to start_agent_test, but the description never says when to call it, when not to, or how it relates to get_agent_test_listener or list_test_scenarios. No preconditions or timing guidance.

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

All Patch MCP 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?