Kubernetes MCP Server

api-resources

Discover available Kubernetes API resources to manage cluster components through natural language commands.

Instructions

Get available API resources

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "api-resources"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:1779-1785 (handler)

Handler for the 'api-resources' tool: executes 'kubectl api-resources' command and returns the output as text content.

case "api-resources": {
  const cmd = `kubectl api-resources`;
  const { stdout } = await execAsync(cmd);
  return {
    content: [{ type: "text", text: stdout || "No API resources found" }]
  };
}

server.js:620-626 (registration)
Registration of the 'api-resources' tool in the tools list, including its name, description, and empty input schema. This list is returned by the ListToolsRequestHandler.
```
  name: "api-resources",
  description: "Get available API resources",
  inputSchema: {
    type: "object",
    properties: {}
  }
},
```
server.js:622-625 (schema)
Input schema for the 'api-resources' tool: an empty object (no parameters required).
```
inputSchema: {
  type: "object",
  properties: {}
}
```

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jan 3, 2026

TDQS

C2.9/5.0

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 available API resources' implies a read-only operation, but it doesn't specify whether this requires authentication, returns structured data, has rate limits, or what format the output takes. 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, clear sentence with no wasted words. It's appropriately sized for a simple tool with no parameters, making it easy to parse and understand quickly.

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 Kubernetes API interactions and the lack of annotations and output schema, the description is insufficient. It doesn't clarify what 'available API resources' entails (e.g., resource types, versions, scopes) or how this differs from other listing tools. For a tool in this context, more detail is needed to guide effective use.

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% (empty schema). The description doesn't need to explain parameters, so it meets the baseline expectation. No additional parameter information is required or provided.

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 available API resources' clearly states the action (get) and target (API resources), but it's vague about what 'available API resources' means in this context. It doesn't distinguish this tool from similar sibling tools like 'api-versions', 'list-all', or 'list-crds' that might also retrieve API-related information.

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 many sibling tools that retrieve Kubernetes resources (e.g., 'list-all', 'list-crds', 'api-versions'), there's no indication of whether this tool is for discovery, listing resource types, or something else. The agent must infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server