Skip to main content
Glama

list-deployments

Retrieve Kubernetes deployments from a specified namespace to monitor and manage application resources in your cluster.

Instructions

List Kubernetes deployments in a namespace

Input Schema

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

Implementation Reference

  • Handler implementation for the 'list-deployments' tool. Executes 'kubectl get deployments' command with optional namespace flag and returns the stdout output.
    case "list-deployments": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get deployments ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No deployments found" }]
      };
    }
  • Tool schema definition including name, description, and inputSchema for 'list-deployments' used in tool registration.
    {
      name: "list-deployments", 
      description: "List Kubernetes deployments in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list deployments from (optional, defaults to current context namespace)"
          }
        }
      }
  • server.js:1392-1394 (registration)
    Registration of the ListToolsRequestHandler which returns the tools array containing 'list-deployments'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the namespace parameter but doesn't describe what the tool actually returns (e.g., deployment names only, full specs, status information), whether it requires specific permissions, or how it handles errors. This leaves significant gaps in understanding the tool's 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 that efficiently communicates the core purpose without any wasted words. It's appropriately sized for a simple listing tool and gets straight to the point.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned about deployments, how results are formatted, whether there are limitations (like pagination), or what happens when the namespace doesn't exist. Given the complexity of Kubernetes deployments and the lack of structured metadata, more context is needed.

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 description mentions 'in a namespace' which aligns with the single parameter, but adds minimal value beyond what the schema already provides (100% coverage with clear description of the namespace parameter). The description doesn't explain namespace semantics beyond what's in the schema description.

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') and resource ('Kubernetes deployments in a namespace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-all' or 'describe-deployment', which would require more specific context about scope or detail level.

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 like 'list-all', 'describe-deployment', and 'get-deployment-metrics' (implied by similar tools), there's no indication of when this specific listing tool is preferred or what its limitations might be.

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