Skip to main content
Glama

list-pvc

List persistent volume claims in a Kubernetes namespace to monitor storage resources and manage cluster capacity.

Instructions

List Kubernetes persistent volume claims in a namespace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to list PVCs from (optional, defaults to current context namespace)

Implementation Reference

  • Handler for the 'list-pvc' tool. Executes 'kubectl get pvc -n [namespace] -o wide' to list PersistentVolumeClaims (PVCs) in the given namespace or default.
    case "list-pvc": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get pvc ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No persistent volume claims found" }]
      };
    }
  • server.js:149-161 (registration)
    Tool registration and schema definition for 'list-pvc' in the tools array, including input schema for optional namespace.
    {
      name: "list-pvc",
      description: "List Kubernetes persistent volume claims in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list PVCs from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • Input schema for the 'list-pvc' tool, defining an optional 'namespace' parameter.
    inputSchema: {
      type: "object",
      properties: {
        namespace: { 
          type: "string",
          description: "The namespace to list PVCs from (optional, defaults to current context namespace)"
        }
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('list') but does not disclose behavioral traits like whether it requires read permissions, returns all PVCs or a filtered subset, handles errors, or includes pagination. This leaves significant gaps for a tool that interacts with a Kubernetes cluster.

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 a single, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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?

Given the complexity of Kubernetes operations and the lack of annotations and output schema, the description is incomplete. It does not cover behavioral aspects like permissions, error handling, or output format, which are crucial for an AI agent to use the tool effectively in this context.

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%, with the single parameter 'namespace' fully documented in the schema. The description does not add any meaning beyond the schema, such as explaining namespace context or default behavior, but the high schema coverage justifies the baseline score of 3.

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 clearly states the verb ('list') and resource ('Kubernetes persistent volume claims in a namespace'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'list-pv' (persistent volumes) or 'list-all', which might list PVCs among other resources, leaving some room for sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'list-all' for broader listings or 'describe-pod' for detailed PVC information, nor does it specify prerequisites such as needing Kubernetes access or namespace permissions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server