Skip to main content
Glama

Control Plane

by io.cpln

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 cannot be set here — apply a full manifest with the CLI (cpln apply; get_resource_schema kind=volumeset first). Changing initialCapacity does not resize existing volumes; expand_volumeset grows them. Recommended reading before first use: get_cpln_skill("stateful-storage") — the runbook for this tool family (read once per session).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gvcYesGVC 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).
orgYesOrganization 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.
nameYesResource name (lowercase kebab-case, starts with a letter, 2-64 chars). Names are IMMUTABLE — renaming = delete + recreate (loses URL, DNS, policy links).
tagsNoAdd or update tags without replacing the full set. Submit an empty list to clear all tags.
snapshotsNoREPLACES the entire snapshot policy — include every field you want to keep (omitted fields are removed).
autoscalingNoREPLACES the entire autoscaling object — include every field you want to keep (omitted fields are removed).
descriptionNoNew description.
mountOptionsNoREPLACES the entire mountOptions object (shared-filesystem volume sets only) — include every field you want to keep.
removeTagKeysNoTag keys to remove from the resource.
initialCapacityNoUpdate the initialCapacity (note: existing volumes do not shrink — expand_volumeset does hot expansion).
removeSnapshotsNotrue deletes spec.snapshots (stops the automatic snapshot schedule).
removeAutoscalingNotrue deletes spec.autoscaling (volumes stop auto-growing).
removeMountOptionsNotrue deletes spec.mountOptions (reverts to platform mount defaults).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary.
summaryYesOne-line summary of the result.
nextStepsNoRecommended follow-up actions for this task, in order.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description discloses critical behavior: snapshots/autoscaling/mountOptions REPLACE entire stored objects, some fields are immutable, and initialCapacity doesn't affect existing volumes. These are non-obvious and valuable caveats not present in annotations.

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?

The description is dense and well-structured, front-loading the main purpose and then listing caveats. It is longer than minimal, but every sentence conveys a distinct fact (replacement semantics, immutability, alternative tools, recommended reading). It earns its length without being verbose.

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 tool's complexity (13 params, nested objects, output schema present), the description covers all critical use-case caveats: replacement behavior, immutable fields, no-resize behavior, alternatives for encryption and expansion, and a pointer to the runbook. An output schema exists, so return-value details are unnecessary.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds some high-level context (e.g., initialCapacity for newly-provisioned volumes, replacement semantics for three objects), but most of this is already embedded in the schema's parameter descriptions. The description doesn't significantly expand beyond what the schema already explains.

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 opens with 'Update mutable volumeset fields' and names the specific mutable fields (description, tags, initialCapacity, snapshot policy, autoscaling, mountOptions). This clearly distinguishes it from siblings like create_volumeset, delete_resource, and expand_volumeset, especially by explicitly pointing to expand_volumeset for growing volumes.

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?

The description gives explicit usage guidance: it states that changing filesystem type/performance class requires snapshot + recreate, that customEncryption must be handled via the CLI manifest, and that initialCapacity changes do not resize existing volumes, directing to expand_volumeset instead. It also recommends reading a skill before first use, effectively describing when to prepare.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Control Plane toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool targets a distinct resource/action pair (e.g., get_resource vs get_resource_schema, list_deployments vs list_workload_replicas) and descriptions clearly differentiate purposes. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern (create_gvc, update_workload, list_resources, query_metrics) with consistent verbs. The few imperative verbs (browse, build, mount) still maintain the same verb-first structure.

Tool Count1/5

With 55 tools, this server far exceeds the typical well-scoped 3-15 tool range. While each tool appears purposeful, the sheer number creates selection overhead and falls into the extreme 50+ category on the rubric.

Completeness4/5

The surface covers nearly the full Control Plane lifecycle: CRUD for GVC, workload, identity, policy, volumeset, and domain, plus observability, templates, image builds, and Terraform. Minor gaps include referenced but missing configure_workload_* tools and no secret creation/deletion (by design).

Resources