Control Plane

Get a Command

get_command

Read-onlyIdempotent

Fetch one asynchronous command (cron run, replica stop, volume set command) by the id the call that started it returned; returns lifecycleStage, messages, and full JSON.

Input Schema

Name	Required	Description
`gvc`	Yes	GVC name.
`org`	No	Organization slug.
`kind`	Yes	Parent resource that owns the command: `workload` (cron runs, replica stops) or `volumeset` (run_volumeset_command). Both are GVC-scoped.
`name`	Yes	Name of the parent workload or volumeset the command was issued against.
`commandId`	Yes	UUID of the command, as returned by the call that started it.

Output 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.

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / commandId / description

Previous value: -"UUID of the command (the `id` field from list_commands, or the Location of the issuing call)."New value: +"UUID of the command, as returned by the call that started it."

changedInput schema / properties / gvc / description

Previous value: -"GVC slug. If the user named none, list_resources (kind \"gvc\") and let them choose."New value: +"GVC name."

changedInput schema / properties / kind / description

Previous value: -"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."New value: +"Parent resource that owns the command: `workload` (cron runs, replica stops) or `volumeset` (run_volumeset_command). Both are GVC-scoped."

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the operation is asynchronous and returns lifecycleStage and messages, signalling a poll-until-terminal pattern.

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 dense sentence with the action, the lookup key, and the return payload front-loaded; no filler or redundancy.

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?

Output schema exists, so return values needn't be detailed, and the annotations carry the safety profile; the description supplies enough about async lifecycle and the id source for the agent to call it correctly. It could note the GVC/parent scoping required by the schema, but that is minor.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a mapping hint by tying the kind values to command types (cron run/replica stop vs volume set command) and restates that commandId comes from the initiating call, which reinforces the schema rather than merely repeating it.

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?

Uses a specific verb (Fetch one) plus a specific resource (asynchronous command) and enumerates concrete command types (cron run, replica stop, volume set command), which separates it from siblings like run_volumeset_command and get_image_build.

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?

Ties usage to the id returned by the call that started the command, which tells the agent this is the follow-up/polling tool for async operations. It doesn't explicitly state when not to use it or name a sibling alternative, so it falls short of a full 5.

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.