Skip to main content
Glama

describe-node

Retrieve detailed information about a specific Kubernetes node, including its status, capacity, and conditions, to monitor cluster health and troubleshoot issues.

Instructions

Describe details of a Kubernetes node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesThe name of the node to describe

Implementation Reference

  • Handler for the 'describe-node' tool. Extracts the 'node' argument, runs 'kubectl describe node <node>', and returns the command output as text content.
    case "describe-node": {
      const { node } = args;
      const cmd = `kubectl describe node ${node}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No node details found" }]
      };
    }
  • Input schema for the 'describe-node' tool, defining a required 'node' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        node: { 
          type: "string",
          description: "The name of the node to describe"
        }
      },
      required: ["node"]
    }
  • server.js:232-244 (registration)
    Registration of the 'describe-node' tool in the tools array, which is returned by the listTools handler. Includes name, description, and input schema.
      name: "describe-node",
      description: "Describe details of a Kubernetes node",
      inputSchema: {
        type: "object",
        properties: {
          node: { 
            type: "string",
            description: "The name of the node to describe"
          }
        },
        required: ["node"]
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'describes details' without specifying what details are returned, whether it's read-only, if it requires specific permissions, or how errors are handled. This is inadequate for a tool that likely returns complex node information.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool.

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 no annotations and no output schema that likely returns detailed node information (status, capacity, conditions), the description is insufficient. It doesn't hint at the complexity of the output or behavioral aspects, leaving significant gaps for an agent to understand what to expect.

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%, so the parameter 'node' is fully documented in the schema. The description adds no additional meaning about the parameter beyond what's in the schema, meeting the baseline for high schema coverage.

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 ('describe details') and resource ('Kubernetes node'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'list-nodes' or 'get-node-metrics', but it's not misleading or tautological.

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 like 'list-nodes' (for overview) or 'get-node-metrics' (for performance data). It lacks any context about prerequisites, typical use cases, or exclusions.

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