Control Plane

Run a Volume Set Command

run_volumeset_command

Destructive

Run one command on one volume of a volume set, picked by location and volumeIndex. expandVolume: grow to newStorageCapacity, live, on any filesystem; at most 4 per volume per rolling 24 hours. shrinkVolume (ext4/xfs): data moves to a smaller volume and the replica restarts; the platform refuses a size below initialCapacity or below used bytes plus 5%. createVolumeSnapshot (ext4/xfs): snapshotName; take one before shrinkVolume, restoreVolume, or deleteVolume, and of the destination volume before copyVolume. restoreVolume (ext4/xfs): a new volume from snapshotName, losing writes since it. deleteVolumeSnapshot: removes that recovery point. deleteVolume (ext4/xfs): its data is lost for good. copyVolume (ext4/xfs): copies the volume to the same index in targetLocation, optionally of targetVolumeSet, deleting the device there. Before shrinkVolume, restoreVolume, deleteVolumeSnapshot, deleteVolume, or copyVolume, tell the user what it removes or replaces, and proceed only on their explicit approval. Runs asynchronously: follow the returned id with get_command. Other settings: update_volumeset.

Input Schema

Name	Required	Description
`gvc`	Yes	GVC name.
`org`	No	Organization slug.
`name`	Yes	Volume set name.
`zone`	No	restoreVolume: availability zone for the new volume; default: the volume's own.
`command`	Yes
`location`	Yes	Location of the volume, e.g. aws-us-east-2.
`volumeIndex`	Yes	Index of the volume in that location; get_resource (kind volumeset) lists each location's volumes.
`snapshotName`	No	createVolumeSnapshot: the new name (lowercase kebab-case). restoreVolume, deleteVolumeSnapshot: an existing snapshot.
`snapshotTags`	No	createVolumeSnapshot: tags for the snapshot.
`expirationDate`	No	createVolumeSnapshot: ISO 8601 expiry, e.g. 2026-04-18T00:00:00Z; default: the volume set's retentionDuration.
`targetLocation`	No	copyVolume: the location the copy is written TO.
`timeoutSeconds`	No	expandVolume, shrinkVolume: seconds to wait for the resize (default 600).
`targetVolumeSet`	No	copyVolume: the volume set that receives the copy, same org: //volumeset/<name>, //gvc/<gvc>/volumeset/<name>, or /org/<org>/gvc/<gvc>/volumeset/<name>; default: this one.
`newStorageCapacity`	No	GB. expandVolume: larger than now. shrinkVolume: smaller, at least 10 (200 for high-throughput-ssd).
`acknowledgeDestinationVolumeDeletion`	No	copyVolume: must be true; the copy deletes and replaces the volume at volumeIndex in the destination.

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.

AddedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: asynchronous execution and following the command id with get_command, expand rate limit of 4 per volume per 24 hours, shrink constraints and replica restart, snapshot/recovery behavior, and irreversible data loss. These details align with destructiveHint=true and are crucial for safe invocation.

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?

Front-loads the core action, then organizes command-specific behavior in compact semicolon-separated clauses. Despite its density, every sentence carries safety, rate-limit, or command-selection information with no filler.

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?

Given 15 parameters, destructive operations, and an output schema, the description covers execution mode, approval requirements, command effects, rate limits, and follow-up via get_command. No essential agent-facing context appears missing.

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 93%, so the baseline is 3, but the description adds meaningful command-specific semantics for newStorageCapacity, snapshotName, targetLocation, targetVolumeSet, and the destructive copy acknowledgement. Some parameters such as org, zone, snapshotTags, and timeout are left largely to the schema.

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 and resource: run one command on one volume selected by location and volumeIndex. It enumerates the seven command types and distinguishes itself from update_volumeset for other settings.

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

Usage Guidelines5/5

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

Gives explicit per-command usage guidance, including when to create a snapshot before destructive commands, when to restore or copy, and when to use update_volumeset instead. It also specifies approval requirements before removal or replacement.

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.