Skip to main content
Glama

list-all

List all Kubernetes resources in a namespace to view cluster contents and manage deployments, pods, and services efficiently.

Instructions

List all Kubernetes resources in a namespace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to list all resources from (optional, defaults to current context namespace)

Implementation Reference

  • The handler function for the 'list-all' tool that executes 'kubectl get all -o wide' in the specified namespace to list all Kubernetes resources.
    case "list-all": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get all ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No resources found" }]
      };
    }
  • The tool metadata including name, description, and input schema definition for the 'list-all' tool, which is part of the tools array registered with the server.
    {
      name: "list-all",
      description: "List all Kubernetes resources in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list all resources from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • server.js:1392-1394 (registration)
    The registration of the tools list handler, which includes the 'list-all' tool in the returned tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 mentions listing resources but fails to disclose behavioral traits like permissions needed, rate limits, output format, pagination, or error handling. This is inadequate for a tool that interacts with a complex system like Kubernetes.

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, making it easy to parse and front-loaded with the core functionality. It efficiently communicates the tool's purpose without unnecessary details.

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 and the lack of annotations and output schema, the description is insufficient. It does not cover behavioral aspects, return values, or usage context, leaving gaps that could hinder an AI agent's ability to use the tool effectively.

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 parameter 'namespace' well-documented as optional with a default. The description adds no additional meaning beyond the schema, such as examples or constraints, but the schema's completeness justifies the baseline score of 3.

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 ('List all') and resource ('Kubernetes resources in a namespace'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'list-pods' or 'list-deployments', which list specific resource types rather than all 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?

The description provides no guidance on when to use this tool versus alternatives, such as more specific listing tools (e.g., 'list-pods' for pods only) or other Kubernetes operations. It lacks context about prerequisites, 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