Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

List Workspace Volumes

listWorkspaceVolumes
Read-only

List a workspace's volumes and service filesystems to inspect storage attached to services, with optional environment and region filters.

Instructions

List a workspace's volumes and service filesystems

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": {
      "workspaceSlug": "<workspaceSlug>"
    },
    "name": "listWorkspaceVolumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond the name — no note on pagination, result scope, permissions, or how 'service filesystems' differ from regular volumes.

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?

A single short sentence with the resource front-loaded and zero filler. It is efficient, though its brevity contributes to the under-specification seen in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three parameters (including an enum), no output schema, and a near-duplicate sibling, this definition is too thin. An agent cannot tell what env or region do, nor how this differs from listVolumes.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate and does not. 'A workspace's' only loosely implies workspaceSlug is the identifier, while the env enum (production/preview/development) and region parameters are never explained at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a workspace's volumes and service filesystems'), which is clear enough for an agent to know what the tool returns. However, it does not distinguish itself from the sibling tool 'listVolumes', which sounds nearly identical, leaving genuine ambiguity about which one to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no reference to the obvious alternative (listVolumes). The agent must infer from the name alone that this is the workspace-scoped variant.

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

Deploy Server

Other Tools