Control Plane

Update a Volumeset

update_volumeset

DestructiveIdempotent

Update mutable volumeset fields: description, tags, initialCapacity (for newly-provisioned volumes), snapshot policy, autoscaling, mountOptions. snapshots/autoscaling/mountOptions REPLACE the entire stored object — include every field you want to keep. Filesystem type and performance class are IMMUTABLE — to change either, snapshot first and recreate. customEncryption: CLI cpln apply only. Changing initialCapacity does not resize existing volumes; expand_volumeset grows them.

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	Add or update tags without replacing the full set. Submit an empty list to clear all tags.
`snapshots`	No	REPLACES the entire snapshot policy: include every field you want to keep. A retentionDuration left out keeps the current one, or 7d when there is none.
`autoscaling`	No	REPLACES the entire autoscaling object — include every field you want to keep (omitted fields are removed).
`description`	No	New description.
`mountOptions`	No	REPLACES the entire mountOptions object (shared-filesystem volume sets only) — include every field you want to keep.
`removeTagKeys`	No	Tag keys to remove from the resource.
`initialCapacity`	No	Update the initialCapacity (note: existing volumes do not shrink — expand_volumeset does hot expansion).
`removeSnapshots`	No	true deletes spec.snapshots (stops the automatic snapshot schedule).
`removeAutoscaling`	No	true deletes spec.autoscaling (volumes stop auto-growing).
`removeMountOptions`	No	true deletes spec.mountOptions (reverts to platform mount defaults).

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.

Changed38 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 / removeTagKeys / items / minLength
```
Removed value: -1
```
removedInput schema / properties / snapshots / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / snapshots / description

Previous value: -"REPLACES the entire snapshot policy — include every field you want to keep (omitted fields are removed)."New value: +"REPLACES the entire snapshot policy: include every field you want to keep. A retentionDuration left out keeps the current one, or 7d when there is none."

removedInput schema / properties / snapshots / properties / retentionDuration / pattern
```
Removed value: -"^([0-9]+(\\.[0-9]+)?[dhm])$"
```
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"
-]New value: +[
+  "gvc",
+  "name"
+]

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

Changed3 schema fields changedAug 21, 2026

addedInput schema / properties / removeAutoscaling

Added value: +{
+  "description": "true deletes spec.autoscaling (volumes stop auto-growing).",
+  "type": "boolean"
+}

addedInput schema / properties / removeMountOptions

Added value: +{
+  "description": "true deletes spec.mountOptions (reverts to platform mount defaults).",
+  "type": "boolean"
+}

addedInput schema / properties / removeSnapshots

Added value: +{
+  "description": "true deletes spec.snapshots (stops the automatic snapshot schedule).",
+  "type": "boolean"
+}

First observedJun 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses the destructive REPLACE semantics of snapshots/autoscaling/mountOptions (a critical data-loss trap that annotations alone don't convey) and the immutability of filesystem type and performance class. This is rich, non-obvious behavioral context beyond the destructiveHint/idempotentHint annotations.

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 mutable fields, then the REPLACE caveat, then the immutable/routing notes. Dense but every sentence carries actionable guidance 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 an output schema exists, return values need not be explained. The description covers the field mutability matrix, replace semantics, and routing to siblings — everything an agent needs to call it correctly.

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 baseline is 3, but the description adds real meaning: replace-vs-merge semantics and the immutable/mutable distinction. It stops short of explaining the remove* toggles, which remain schema-only.

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?

Opens with a specific verb+resource ("Update mutable volumeset fields") and enumerates exactly which fields are mutable. It also distinguishes itself from expand_volumeset by name, so an agent can select it without opening the schema.

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?

Explicitly routes the agent: immutable fields require "snapshot first and recreate," initialCapacity does not resize existing volumes so use expand_volumeset, and customEncryption must go through the CLI. Both when-to-use-this and when-to-use-alternatives are covered.

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.