Skip to main content
Glama
This connector has been deprecated

Replaced by Control Plane.

This listing has been renamed. Control Plane is now listed as com.controlplane/mcp.

It is the same server at the same endpoint (https://mcp.cpln.io/mcp), so existing connections keep working. Please use the new listing going forward.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gvc": "<gvc>",
      "workloadName": "<workloadName>"
    },
    "name": "mount_volumeset_to_workload"
  }
}

Input Schema

NameRequiredDescriptionDefault
gvcYesGVC name.
orgNoOrganization slug.
sizeNoInitial capacity in GB, CREATE-ONLY (ignored when the volumeset already exists; run_volumeset_command expandVolume grows it). Required when creating. Min 10 (200 for high-throughput-ssd), max 65536.
tagsNoOptional tags for the volumeset; use them like Kubernetes labels for governance and search.
mountPathNoMount path inside the container (defaults to /mnt/{volumesetName}). Normalized before validation (".." resolved, "//" collapsed); reserved paths /dev, /dev/log, /tmp, /var, /var/log are rejected.
descriptionNoVolumeset description so operators know what data lives here (treat it like a Kubernetes annotation).
workloadNameYesExisting workload name to mount storage into; pass the name only, not a link.
volumesetNameNoOptional 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.
fileSystemTypeNoFile 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).
performanceClassNoPerformance 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

NameRequiredDescriptionDefault
okYes
dataNoThe full result. Read this, not only the summary.
detailsNo
summaryYes
nextStepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / recoveryPolicy
      Removed value: -{
      -  "description": "What a NEW replica does when a matching volume already exists: \"retain\" (default) reuses the data, \"recycle\" starts fresh (schema/volumeSpec recoveryPolicy).",
      -  "enum": [
      -    "retain",
      -    "recycle"
      -  ],
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • changedInput schema / properties / gvc / description
      Previous value: -"GVC slug. If the user named none, list_resources (kind \"gvc\") and let them choose."New value: +"GVC name."
    • changedInput schema / properties / size / description
      Previous value: -"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."New value: +"Initial capacity in GB, CREATE-ONLY (ignored when the volumeset already exists; run_volumeset_command expandVolume grows it). Required when creating. Min 10 (200 for high-throughput-ssd), max 65536."
  3. Changed29 schema fields changed
    • 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."
  4. First observed

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 rich behavior: the mount is added to the FIRST container, existing mounts and stored data remain, in-use mount paths are refused, read-write-once volumesets used by another workload are refused, and the workload rolls out again. It also explains create-only parameter behavior and workload-type binding rules, adding substantial value over the annotation hints.

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 front-loaded and every clause earns its place: purpose first, then additive behavior, refusal conditions, create-path caveats, and workload-type rules. Despite its length, it is appropriately structured for a complex mutation tool with 10 parameters.

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 complexity of mounting storage, creating a volumeset when missing, and enforcing workload-type constraints, the description covers the critical decision points an agent needs. An output schema exists and annotations cover safety/idempotency, so return values and basic safety do not need further explanation here.

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 the schema already documents parameters thoroughly. The description adds some useful high-level semantics, especially that size/fileSystemType/performanceClass apply only when creating a missing volumeset and that ext4/xfs volumesets bind to one workload, though much of this repeats schema-level create-only notes.

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 and resource: 'Attach a volumeset to a workload by adding a mount to its FIRST container.' It clearly distinguishes the operation from sibling volume tools like update_volumeset and run_volumeset_command by focusing on the mount/attach 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 usage context: existing mounts and data are preserved, in-use mount paths are refused, read-write-once volumesets used elsewhere are refused, and workload-type rules constrain which workloads can mount which filesystems. It does not explicitly name alternative tools for related operations, but the conditions for calling this tool are well stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.