Control Plane

Get a Command

get_command

Read-onlyIdempotent

Fetch one asynchronous command (cron run, replica stop, volume expand, shrink, snapshot, restore, delete) by the id from list_commands; returns lifecycleStage, messages, and full JSON.

Input Schema

TableJSON Schema

Name	Required	Description
`gvc`	Yes	GVC slug. If the user named none, list_resources (kind "gvc") and let them choose.
`org`	No	Organization slug.
`kind`	Yes	Parent resource that owns the command — `workload` (cron runs via workload_start_cron, replica stops via workload_stop_replica) or `volumeset` (volume expand / shrink / snapshot / restore / delete). Both are GVC-scoped.
`name`	Yes	Name of the parent workload or volumeset the command was issued against.
`commandId`	Yes	UUID of the command (the `id` field from list_commands, or the Location of the issuing call).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / gvc / description

Previous value: -"GVC slug (lowercase kebab-case). Use the GVC the user named; otherwise discover with list_resources (kind=\"gvc\") and let them choose — never guess (a wrong GVC targets the wrong environment)."New value: +"GVC slug. If the user named none, list_resources (kind \"gvc\") and let them choose."

removedInput schema / properties / gvc / maxLength
```
Removed value: -63
```
removedInput schema / properties / gvc / minLength
```
Removed value: -1
```

removedInput schema / properties / gvc / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

removedInput schema / properties / name / maxLength
```
Removed value: -64
```
removedInput schema / properties / name / minLength
```
Removed value: -2
```
removedInput schema / properties / name / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```

changedInput schema / properties / org / description

Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."

removedInput schema / properties / org / maxLength
```
Removed value: -63
```
removedInput schema / properties / org / minLength
```
Removed value: -1
```

removedInput schema / properties / org / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

changedInput schema / required

Previous value: -[
-  "org",
-  "kind",
-  "gvc",
-  "name",
-  "commandId"
-]New value: +[
+  "kind",
+  "gvc",
+  "name",
+  "commandId"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / data / description

Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."

addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / nextSteps / description

Removed value: -"Recommended follow-up actions for this task, in order."

removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```

AddedAug 14, 2026

TDQS

A4/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 that the tool targets asynchronous operations and what lifecycle fields come back, which helps an agent understand it as a poll-status primitive, but it doesn't add beyond-annotation behavior such as retention or eventual-consistency caveats.

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?

One tightly packed sentence that front-loads the verb and scope and closes with the return shape. No waste, nothing redundant or hedged.

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 a full output schema, complete schema descriptions, and annotations covering safety and idempotency, the definition is nearly self-sufficient. The only minor gap is no guidance on what to do when a command id is stale or not found.

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 five params (including the kind enum and commandId UUID) are already documented in the schema, and the description's mention of 'the id from list_commands' duplicates the commandId description. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (Fetch) and resource (one asynchronous command) with concrete examples of command types (cron run, replica stop, volume expand, etc.). The phrase 'by the id from list_commands' clearly separates it from the sibling list_commands, which enumerates rather than retrieves one.

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?

Explicitly points to list_commands as the source of the id, giving a clear retrieval workflow. It doesn't state exclusions or failure cases (e.g., what happens if the command has aged out), but the context for use is unambiguous.

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

All Control Plane 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.