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 (customer-managed KMS keys) cannot be set here — apply a full manifest with the CLI (cpln apply), calling get_resource_schema (kind=volumeset) first. Mount separately via mount_volumeset_to_workload (ext4/xfs need a stateful or vm workload; shared mounts on any workload type). Recommended reading before first use: get_cpln_skill("stateful-storage") — the runbook for this tool family (read once per session).

Input Schema

TableJSON Schema

Name	Required	Description
`gvc`	Yes	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).
`org`	Yes	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.
`name`	Yes	Resource name (lowercase kebab-case, starts with a letter, 2-64 chars). Names are IMMUTABLE — renaming = delete + recreate (loses URL, DNS, policy links).
`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	Whether the call succeeded.
`data`	No	The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary.
`summary`	Yes	One-line summary of the result.
`nextSteps`	No	Recommended follow-up actions for this task, in order.

TDQS

A5/5.0

Behavior5/5

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

Discloses many behavioral traits beyond the sparse annotations (readOnlyHint=false, destructiveHint=false): performance class and filesystem type are immutable, snapshot defaults are injected (createFinalSnapshot=true, retentionDuration '7d'), and xfs/ext4 support snapshots while shared does not. These details give the agent essential expectations about side effects and constraints that the annotations do not cover.

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 front-loaded with the core purpose and every subsequent sentence earns its place by adding distinct, high-value information (immutability, snapshot defaults, encryption limitation, mounting guidance, reading recommendation). While long, the length is justified by the tool's complexity and no sentence is redundant.

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 (12 params, nested objects, output schema), the description covers key constraints, defaults, exclusions, and cross-references to related tools and documentation. It provides enough context for correct invocation and successful execution without needing to describe return values since an output schema exists.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds meaningful semantic context by highlighting which parameters are most important (performance class, filesystem type, initial capacity, snapshot policy, autoscaling) and by explaining immutability implications and default injection behavior. This goes beyond what the schema parameter descriptions already state.

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 a specific verb+resource: 'Create a new volumeset in a GVC with explicit performance class, filesystem type, initial capacity, snapshot policy, and (optional) autoscaling.' It clearly names the action and key settings, and differentiates from related tools by stating 'Mount separately via mount_volumeset_to_workload,' making the purpose unambiguous.

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?

Provides explicit when-not-to-use guidance: customEncryption cannot be set here and requires `cpln apply` with a full manifest, plus it names the alternative tool for mounting (mount_volumeset_to_workload) and clarifies workload type restrictions (ext4/xfs need stateful or vm; shared mounts anywhere). Also recommends reading get_cpln_skill('stateful-storage') before first use, effectively explaining a prerequisite.

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

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).

Create a Volumeset

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources