mcp

Get run

get_run

Read-only

One run: its status, every resource linked to it (with when each was removed), its checkpoints (each with its status and the machines it saved) and, once it has ended, its end report: what was removed, anything that could not be, and why. After end_run, call this until status is ended or end_failed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_run"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The run's id, from create_run or list_runs.

Output Schema

Name	Required	Description	Default
`run`	No
`mode`	No
`error`	No
`status`	No
`details`	No
`message`	No
`recovery`	No
`validation`	No
`account_notices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 5, 2026
- addedOutput schema / properties / details
```
Added value: +{}
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recovery
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / validation
```
Added value: +{}
```
AddedNov 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds real value by disclosing that the end report only materializes once the run has ended and by outlining what each section reports (what was removed and what could not be, plus why). It does not mention rate limits, polling cadence, or payload size for runs with many resources.

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?

A single dense sentence front-loads the resource ('One run') and then enumerates contents, followed by a short imperative polling directive. Slightly list-heavy but every clause carries information; nothing is pad.

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?

For a one-parameter read tool with an output schema, the description covers what the agent needs: what comes back at a high level, that the end report is conditional on termination, and the exact polling loop to run after end_run. Return-value detail is correctly left to the output 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 coverage is 100% and the schema already documents that id is the run's UUID sourced 'from create_run or list_runs'. The description adds no additional meaning about the id parameter, so the baseline of 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+resource ('One run') and enumerates exactly what the payload contains: status, linked resources with removal timestamps, checkpoints with status and machines, and an end report. The singular framing implicitly distinguishes it from list_runs, though it never names that sibling explicitly.

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 a concrete operational rule: 'After end_run, call this until status is ended or end_failed,' which tells the agent when to poll and when to stop. It provides no guidance on choosing this over siblings like list_runs, pause_run, or get_deployment, so the when-not side is absent.

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

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