Control Plane

Create a Volumeset

create_volumeset

Create a new volumeset in a GVC with explicit performance class, filesystem type, initial capacity, snapshot policy, and (optional) autoscaling. Performance class and filesystem type are IMMUTABLE — choose carefully. xfs/ext4 support snapshots; shared is read-write-many but cannot be snapshotted. Snapshot defaults injected when omitted: createFinalSnapshot=true, retentionDuration "7d". customEncryption: CLI cpln apply only. Mount separately via mount_volumeset_to_workload (ext4/xfs need a stateful or vm workload; shared mounts 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.
`name`	Yes	Resource name. Immutable: renaming is delete and recreate.
`tags`	No	Optional tags (treat like Kubernetes labels for governance and search).
`snapshots`	No	Snapshot policy.
`autoscaling`	No	Reactive + predictive autoscaling settings.
`description`	No	Volumeset description so operators know what data lives here.
`mountOptions`	No	Mount options — only for shared-filesystem volume sets (resources provisioned per mount point).
`fileSystemType`	No	Filesystem type. Immutable. xfs/ext4 support snapshots; shared is RWX without snapshots (default xfs).
`initialCapacity`	Yes	Initial capacity in GB. Performance-class minimums apply (general-purpose-ssd ≥10, high-throughput-ssd ≥200). Max 65536.
`performanceClass`	No	Performance class. Immutable after creation — choose carefully (default general-purpose-ssd).
`storageClassSuffix`	No	Self-hosted location override for storage class lookup.

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.

Changed37 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 / autoscaling / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / autoscaling / properties / predictive / 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 / mountOptions / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / mountOptions / properties / resources / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / mountOptions / properties / resources / properties / maxCpu / pattern
```
Removed value: -"^([0-9]+)(m|(\\.[0-9]{1,3}))?$"
```
- removedInput schema / properties / mountOptions / properties / resources / properties / maxMemory / pattern
```
Removed value: -"^[0-9]+(\\.[0-9]{1,3})?(G|M|k|Gi|Mi|Ki)?$"
```
- removedInput schema / properties / mountOptions / properties / resources / properties / minCpu / pattern
```
Removed value: -"^([0-9]+)(m|(\\.[0-9]{1,3}))?$"
```
- removedInput schema / properties / mountOptions / properties / resources / properties / minMemory / pattern
```
Removed value: -"^[0-9]+(\\.[0-9]{1,3})?(G|M|k|Gi|Mi|Ki)?$"
```
- changedInput schema / properties / name / description
```
Previous value: -"Resource name (lowercase kebab-case, starts with a letter, 2-64 chars). Names are IMMUTABLE — renaming = delete + recreate (loses URL, DNS, policy links)."New value: +"Resource name. Immutable: renaming is delete and recreate."
```
- 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])?$"
```
- removedInput schema / properties / snapshots / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / snapshots / properties / retentionDuration / pattern
```
Removed value: -"^([0-9]+(\\.[0-9]+)?[dhm])$"
```
- removedInput schema / properties / storageClassSuffix / pattern
```
Removed value: -"^[a-zA-Z][0-9a-zA-Z\\-_]*$"
```
- 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
```
- changedInput schema / required
```
Previous value: -[
-  "org",
-  "gvc",
-  "name",
-  "initialCapacity"
-]New value: +[
+  "gvc",
+  "name",
+  "initialCapacity"
+]
```
- 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.6/5.0

Behavior5/5

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

Annotations only mark this as a non-read-only, non-destructive write. The description adds substantial behavioral detail beyond that: immutability of performance class and filesystem type, injected snapshot defaults (createFinalSnapshot=true, retentionDuration "7d"), the filesystem/snapshot capability matrix, and a caveat that customEncryption is CLI-only. This is exactly the extra context a caller needs.

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?

Front-loads the core action, then packs constraints into short clauses with no filler; each sentence carries a decision-relevant fact. It is dense and slightly run-on, but nothing is wasted.

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 12-parameter tool with nested objects and an output schema present, the description covers the critical ambiguities: immutability, default behavior on omission, filesystem capability differences, and the separate mount step. Nothing an agent needs to invoke it correctly is 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 already 100%, so the baseline is 3, but the description adds meaning the schema does not: default injection for snapshots, the semantic split of xfs/ext4 vs shared, and mount-type constraints tied to fileSystemType. It stops short of explaining a few params (e.g. storageClassSuffix, mountOptions.resources defaults) but those are covered by 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+resource ("Create a new volumeset in a GVC") and enumerates the key configurable dimensions (performance class, filesystem type, capacity, snapshot policy, autoscaling). It distinguishes itself from siblings like update_volumeset/expand_volumeset by being the creation entry point and explicitly hands off to mount_volumeset_to_workload.

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 clear decision context: performance class and filesystem type are immutable so must be chosen carefully, xfs/ext4 support snapshots while shared does not, and mounting happens separately via mount_volumeset_to_workload with workload-type constraints. It does not explicitly contrast with update_volumeset or expand_volumeset, so the when-not-to-use-this guidance is implied rather than stated.

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.