Skip to main content
Glama

cluster-info

Retrieve essential Kubernetes cluster details including nodes, versions, and status to monitor infrastructure health and configuration.

Instructions

Get cluster information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'cluster-info' tool. It runs the 'kubectl cluster-info' command using execAsync and returns the standard output as text content in the MCP response format.
      const cmd = `kubectl cluster-info`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "Unable to get cluster info" }]
      };
    }
  • The tool schema definition for 'cluster-info', including name, description, and empty input schema. This is part of the tools array returned by ListToolsRequestHandler.
      name: "cluster-info",
      description: "Get cluster information",
      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. It states 'Get cluster information', implying a read-only operation, but doesn't disclose behavioral traits like what type of information is returned, format, permissions needed, or potential side effects. This is inadequate for a tool with zero annotation coverage.

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 extremely concise ('Get cluster information') with no wasted words, making it front-loaded and easy to parse. However, this conciseness comes at the cost of detail, but it efficiently communicates the core purpose.

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 cluster operations and no annotations or output schema, the description is incomplete. It doesn't explain what 'cluster information' entails, the return format, or how it differs from similar tools, leaving significant gaps for an agent to use it effectively.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, earning a baseline score of 4 for matching the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get cluster information' clearly states the verb ('Get') and resource ('cluster information'), but it's vague about what specific information is retrieved. It doesn't distinguish from sibling tools like 'get-cluster-metrics' or 'list-nodes', which also provide cluster-related data.

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. With many sibling tools that might overlap (e.g., 'get-cluster-metrics', 'list-nodes'), the description lacks context about when this specific tool is appropriate, leaving the agent to guess.

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