Skip to main content
Glama

get-crd

Retrieve custom resource definitions from Kubernetes clusters to view their structure and configuration details.

Instructions

Get a custom resource definition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the CRD

Implementation Reference

  • The execution handler for the 'get-crd' tool. It runs 'kubectl get crd [name] -o yaml' and returns the stdout as text content.
      const { name } = args;
      const cmd = `kubectl get crd ${name} -o yaml`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "CRD not found" }]
      };
    }
  • The tool schema and registration entry in the tools array, defining the name, description, and input schema (requiring 'name' parameter).
    {
      name: "get-crd",
      description: "Get a custom resource definition",
      inputSchema: {
        type: "object",
        properties: {
          name: { 
            type: "string",
            description: "The name of the CRD"
          }
        },
        required: ["name"]
      }
    },
  • server.js:1392-1394 (registration)
    The server request handler for listing tools, which returns the full 'tools' array including the 'get-crd' tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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. 'Get' implies a read operation, but it doesn't specify whether this requires specific permissions, returns structured data or raw YAML, handles errors for non-existent CRDs, or has any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with zero wasted words. It's front-loaded with the core purpose ('Get a custom resource definition'), making it immediately clear 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 lack of annotations and output schema, the description is incomplete for a tool that likely returns detailed CRD information. It doesn't explain what 'Get' entails—whether it returns YAML, JSON, metadata, or validation schema—leaving the agent to guess about the response format and usage context in a complex Kubernetes environment.

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?

The schema description coverage is 100%, with the 'name' parameter clearly documented in the schema. The description doesn't add any additional meaning about the parameter (e.g., format examples like 'example.com/v1' or case sensitivity), so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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 action ('Get') and resource ('custom resource definition'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list-crds' or 'describe-configmap', which would require more specific context about what makes this tool unique.

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 siblings like 'list-crds' (for listing CRDs) and 'describe-configmap' (for detailed descriptions of resources), there's no indication whether this tool retrieves a single CRD by name, provides detailed metadata, or serves a different purpose entirely.

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