Skip to main content
Glama

k8s_describe_node

Retrieve comprehensive Kubernetes node details including resource capacity, allocatable resources, system conditions, and taints for infrastructure management and troubleshooting.

Instructions

Get detailed node info including capacity, allocatable resources, conditions, and taints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNode name

Implementation Reference

  • The handler function 'describeNode' which queries the Kubernetes API for detailed node information.
    export async function describeNode(args: Record<string, unknown>): Promise<string> {
      const api = getCoreV1Api();
      const name = args.name as string;
    
      if (!name) throw new Error("Node name is required");
    
      const response = await api.readNode(name);
      const node = response.body;
    
      const allocatable = node.status?.allocatable || {};
      const capacity = node.status?.capacity || {};
    
      const lines: string[] = [
        `Name:         ${node.metadata?.name}`,
        `OS:           ${node.status?.nodeInfo?.osImage || "?"}`,
        `Kernel:       ${node.status?.nodeInfo?.kernelVersion || "?"}`,
        `Runtime:      ${node.status?.nodeInfo?.containerRuntimeVersion || "?"}`,
        `Kubelet:      ${node.status?.nodeInfo?.kubeletVersion || "?"}`,
        "",
        "Capacity:",
        `  CPU:         ${capacity.cpu || "?"}`,
        `  Memory:      ${capacity.memory || "?"}`,
        `  Pods:        ${capacity.pods || "?"}`,
        "",
        "Allocatable:",
        `  CPU:         ${allocatable.cpu || "?"}`,
        `  Memory:      ${allocatable.memory || "?"}`,
        `  Pods:        ${allocatable.pods || "?"}`,
        "",
        "Conditions:",
      ];
    
      for (const cond of node.status?.conditions || []) {
        lines.push(`  ${cond.type}: ${cond.status} — ${cond.message || ""}`);
      }
    
      const taints = node.spec?.taints || [];
      if (taints.length > 0) {
        lines.push("", "Taints:");
        for (const taint of taints) {
  • The definition and input schema for the 'k8s_describe_node' tool.
    {
      name: "k8s_describe_node",
      description: "Get detailed node info including capacity, allocatable resources, conditions, and taints",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: { type: "string", description: "Node name" },
        },
        required: ["name"],
      },
    },
  • The switch case that dispatches the 'k8s_describe_node' tool name to its handler implementation.
    case "k8s_describe_node": return describeNode(a);
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 tool retrieves information ('Get'), implying it's a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or output format. For a tool with no annotations, this leaves significant gaps in understanding how it behaves beyond basic purpose.

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 front-loads the core action ('Get detailed node info') and lists key details without unnecessary words. Every part earns its place by specifying the information retrieved, making it easy to scan and understand quickly.

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?

Given the tool's moderate complexity (a read operation with one parameter) and no annotations or output schema, the description is minimally complete. It covers the purpose and key data points but lacks behavioral context and usage guidance. For a tool without structured safety or output information, more detail would be beneficial to fully inform an agent.

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 input schema has 100% description coverage, with the 'name' parameter documented as 'Node name'. The description doesn't add any parameter-specific semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 ('Get') and resource ('detailed node info'), specifying what information is retrieved (capacity, allocatable resources, conditions, taints). It distinguishes from siblings like 'k8s_get_nodes' by focusing on detailed information for a specific node rather than listing nodes. However, it doesn't explicitly contrast with 'k8s_describe_pod' for similar describe operations on different resources.

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?

No guidance is provided on when to use this tool versus alternatives. While the description implies it's for detailed node information, it doesn't mention when to choose this over 'k8s_get_nodes' (for listing) or 'k8s_top_nodes' (for resource usage), nor does it specify prerequisites like needing node names from other tools. The context is implied but not explicit.

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/batu-sonmez/infraclaude'

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