Skip to main content
Glama

list-namespaces

Lists all Kubernetes namespaces to help users identify and manage cluster resources through AI assistants.

Instructions

List all Kubernetes namespaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list-namespaces' tool within the CallToolRequestSchema handler. It executes the kubectl command to list all namespaces and returns the output as text content.
    case "list-namespaces": {
      const cmd = `kubectl get namespaces -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No namespaces found" }]
      };
    }
  • The schema definition for the 'list-namespaces' tool in the tools array, specifying name, description, and empty input schema (no parameters required).
    {
      name: "list-namespaces",
      description: "List all Kubernetes namespaces",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • server.js:1392-1394 (registration)
    Registration of the ListToolsRequestSchema handler that returns the full list of tools, including 'list-namespaces'.
    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 of behavioral disclosure. It states the action ('List all') but doesn't mention permissions required, rate limits, pagination, output format, or any side effects. For a read operation in a complex system like Kubernetes, this lack of detail is a significant gap.

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 front-loaded with the core action and resource, making it highly efficient and easy to parse for an AI agent.

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 operations and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, output structure, or error handling, which are crucial for effective tool use in this context.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the schema completeness, aligning with the baseline for zero parameters.

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 'List all Kubernetes namespaces' clearly states the verb ('List') and resource ('Kubernetes namespaces'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list-all' or 'list-pods' beyond specifying the resource type, which is adequate but not optimal for sibling distinction.

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 siblings like 'list-all' (which might list all resources) and 'create-namespace' (for creation), there's no explicit or implied context for choosing this specific listing tool, leaving the agent without usage direction.

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