Skip to main content
Glama

Get PVCs

get_pvcs
Read-only

Fetch PersistentVolumeClaim summary rows: name, namespace, status, bound volume, storage class, access modes, capacity and requested size. Unbound claims sort first. A list needs namespace or all_namespaces=true and carries total, returned, truncated and scope.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_pvcs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific PVC name to fetch.
namespaceNoKubernetes namespace to list. A list needs either this or all_namespaces=true; a named read (name) needs neither.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
all_namespacesNoSet true to list every namespace on the cluster deliberately. Omit it and pass namespace to list one namespace; a list with neither is refused (error_code scope_required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description adds genuinely useful behavior: unbound claims sort first, a scope-less list is refused, and the response carries total/returned/truncated/scope. With no output schema, disclosing the truncation envelope is valuable. It still doesn't say how large a page is or how to retrieve the remainder.

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?

Two tight sentences: returned fields first, then ordering, then the scoping rule and response envelope. Every clause carries information and nothing is padded.

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

Completeness4/5

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

For a read-only list/get tool with no output schema, the description covers what comes back, how results are ordered, and the scoping precondition, which is close to complete. The remaining gap is pagination mechanics — how much is returned before truncation and how to fetch more.

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 coverage is 100%, so every parameter already carries its own description, including the scope_required error and the named-read exemption — the description largely restates that rule. The only added meaning is the ordering guarantee for unbound claims, which is marginal against a fully documented schema.

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?

The description opens with a specific verb+resource ("Fetch PersistentVolumeClaim summary rows") and enumerates the exact fields returned (name, namespace, status, bound volume, storage class, access modes, capacity, requested size), which clearly separates it from get_pods, get_statefulsets, or describe_resource. It stops short of naming any sibling tool or when to prefer one, so it lands just under a 5.

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?

"A list needs namespace or all_namespaces=true" and the distinction between a list and a named read give concrete conditions for calling it. What's absent is guidance on alternatives — e.g. when to use describe_resource or get_storage_class instead of this summary view — so there are no explicit exclusions.

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.