Skip to main content
Glama

list-crds

List Kubernetes custom resource definitions to discover and manage extended API resources in your cluster.

Instructions

List Kubernetes custom resource definitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list-crds' tool. It executes the kubectl command 'kubectl get crds -o wide' using execAsync and returns the output as text content.
      const cmd = `kubectl get crds -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No custom resource definitions found" }]
      };
    }
  • server.js:957-963 (registration)
    Registration of the 'list-crds' tool in the tools array, which is returned by the ListToolsRequestHandler. Includes the tool name, description, and empty input schema.
      name: "list-crds",
      description: "List Kubernetes custom resource definitions",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Input schema for the 'list-crds' tool, which expects no parameters (empty properties).
    inputSchema: {
      type: "object",
      properties: {}
    }
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 of behavioral disclosure. While 'List' implies a read operation, the description doesn't specify whether this requires specific permissions, what format the output takes, whether it's paginated, or if there are any rate limits. For a tool with zero annotation coverage, this represents significant gaps in behavioral understanding.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple listing tool and gets straight to the point with no unnecessary elaboration.

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

Completeness3/5

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

For a zero-parameter listing tool with no output schema, the description provides the minimum viable information about what the tool does. However, without annotations or output schema, it doesn't address important behavioral aspects like output format, permissions needed, or how it differs from similar sibling tools, leaving gaps in contextual understanding.

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?

With 0 parameters and 100% schema description coverage, the baseline score would be 4 even with no parameter information in the description. The description appropriately doesn't mention parameters since none exist, which is correct for this tool.

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 custom resource definitions'), making the purpose immediately understandable. However, it doesn't differentiate from similar sibling tools like 'list-all' or 'get-crd', which could cause confusion about when to use this specific tool versus alternatives.

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. With sibling tools like 'list-all' (which might include CRDs) and 'get-crd' (which might retrieve a specific CRD), the agent has no indication of when this particular listing tool is appropriate versus those other options.

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