Control Plane

Mount Volumeset to Workload

mount_volumeset_to_workload

Idempotent

Attach a volumeset to a workload by adding a mount to its FIRST container. Additive: existing mounts and stored data stay as they are, a mount path already in use is refused, and a read-write-once volumeset another workload uses is refused; the workload rolls out again to pick up the mount. Creates the volumeset when missing; size/fileSystemType/performanceClass apply ONLY on that create path and are ignored when the volumeset already exists. Workload-type rule: ext4/xfs (read-write-once) volumesets require a stateful or vm workload and bind to ONE workload; shared-filesystem volumesets mount on any workload type.

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.
`size`	No	Initial capacity in GB — CREATE-ONLY (ignored when the volumeset already exists; expand_volumeset grows it). Required when creating. Min 10 (200 for high-throughput-ssd), max 65536.
`tags`	No	Optional tags for the volumeset; use them like Kubernetes labels for governance and search.
`mountPath`	No	Mount path inside the container (defaults to /mnt/{volumesetName}). Normalized before validation (".." resolved, "//" collapsed); reserved paths /dev, /dev/log, /tmp, /var, /var/log are rejected.
`description`	No	Volumeset description so operators know what data lives here (treat it like a Kubernetes annotation).
`workloadName`	Yes	Existing workload name to mount storage into; pass the name only, not a link.
`volumesetName`	No	Optional volumeset resource name, not a link. Omit to use {workloadName}-vol. If this volumeset does not exist yet, `size` is required so the tool can create it before mounting.
`fileSystemType`	No	File system type — CREATE-ONLY (ignored when the volumeset already exists); default xfs. ext4/xfs are read-write-once (stateful or vm workloads only); shared is read-write-many (any workload type).
`recoveryPolicy`	No	What a NEW replica does when a matching volume already exists: "retain" (default) reuses the data, "recycle" starts fresh (schema/volumeSpec recoveryPolicy).
`performanceClass`	No	Performance class — CREATE-ONLY (ignored when the volumeset already exists); default general-purpose-ssd. high-throughput-ssd requires size ≥ 200; shared pairs only with fileSystemType shared.

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.

Changed29 schema fields changedSep 30, 2026

removedInput schema / $schema

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

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / description / maxLength
```
Removed value: -250
```

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 / mountPath / minLength
```
Removed value: -1
```

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])?$"

removedInput schema / properties / tags / items / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / tags / items / properties / key / minLength
```
Removed value: -1
```
removedInput schema / properties / tags / maxItems
```
Removed value: -50
```
removedInput schema / properties / volumesetName / maxLength
```
Removed value: -64
```
removedInput schema / properties / volumesetName / minLength
```
Removed value: -2
```
removedInput schema / properties / volumesetName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```
removedInput schema / properties / workloadName / maxLength
```
Removed value: -64
```
removedInput schema / properties / workloadName / minLength
```
Removed value: -2
```
removedInput schema / properties / workloadName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```

changedInput schema / required

Previous value: -[
-  "org",
-  "gvc",
-  "workloadName"
-]New value: +[
+  "gvc",
+  "workloadName"
+]

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."
```

First observedJun 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: mounts to the first container only, additive changes that preserve existing mounts and data, specific refusal conditions, a workload rollout after mounting, automatic volumeset creation when missing, and create-only semantics for size/fileSystemType/performanceClass. These details substantially aid 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?

The description is dense but well-structured and front-loaded with the primary action. Each sentence carries necessary behavioral or constraint 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 the complex 11-parameter mutation operation, rich schema coverage, existing output schema, and provided annotations, the description is complete enough for correct selection and invocation. It covers the key behavioral caveats, create-path conditions, and workload-type rules.

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 already 100%, so the baseline is 3. The description adds cross-parameter meaning by tying size/fileSystemType/performanceClass to the create path only and summarizing workload-type compatibility, which helps an agent understand parameter interactions beyond individual schema descriptions.

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?

The description states a specific verb and resource: attaching/mounting a volumeset to a workload by adding a mount to its first container. It clearly distinguishes the operation from sibling create/update volumeset tools and immediately conveys the core action.

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?

The description gives clear conditions for use and refusal: additive behavior, refusal when a mount path is already in use, refusal for read-write-once volumesets already bound to another workload, and workload-type compatibility rules. It does not explicitly name alternative siblings or say when to prefer create_volumeset/update_volumeset instead, but it supplies strong operational context.

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.