Skip to main content
Glama
Flux159
by Flux159

explain_resource

Read-only

Retrieve documentation for a Kubernetes resource or field by specifying the name or field path, with optional API version and recursive field details.

Instructions

Get documentation for a Kubernetes resource or field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYesResource name or field path (e.g. 'pods' or 'pods.spec.containers')
apiVersionNoAPI version to use (e.g. 'apps/v1')
recursiveNoPrint the fields of fields recursively
contextNoKubeconfig Context to use for the command (optional - defaults to null)
outputNoOutput format (plaintext or plaintext-openapiv2)plaintext

Implementation Reference

  • TypeScript interface for ExplainResourceParams. Defines the shape of parameters accepted by explainResource handler: resource (required string), apiVersion (optional string), recursive (optional boolean), output (optional 'plaintext'|'plaintext-openapiv2'), context (optional string).
    export interface ExplainResourceParams {
      resource: string;
      apiVersion?: string;
      recursive?: boolean;
      output?: "plaintext" | "plaintext-openapiv2";
      context?: string;
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's claim 'Get documentation' is consistent. However, the description does not add behavioral context such as network requirements, return type, or effect on cluster state beyond what annotations provide.

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?

A single, front-loaded sentence with no redundant information. Every word is necessary, making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, the description is mostly complete. It covers the core functionality, and the input schema covers parameter details. However, it omits the output format (which is not in output schema) and the fact that it returns documentation text, but this is minor for a read-only tool.

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?

Input schema has 100% coverage with descriptions for each parameter. The description does not enrich parameter meanings; it only hints at the purpose of the 'resource' parameter by mentioning 'resource or field'. Baseline 3 is appropriate as schema already documents parameters well.

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 uses a specific verb 'Get' and resource 'documentation for a Kubernetes resource or field', clearly indicating the tool's function. It distinguishes from sibling tools like kubectl_describe (which provides details on a running resource) and kubectl_get (which retrieves resources), though not explicitly.

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 on when to use this tool versus alternatives such as list_api_resources or kubectl_describe. The description lacks conditions, prerequisites, or exclusions, providing no help for the agent to decide.

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/Flux159/mcp-server-kubernetes'

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