Skip to main content
Glama

list-ingresses

Retrieve Kubernetes ingress configurations from a specified namespace to manage network routing and access rules for applications.

Instructions

List Kubernetes ingresses in a namespace

Input Schema

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

Implementation Reference

  • Handler function that executes the kubectl command to list Kubernetes ingresses in the specified or default namespace, returning the output.
    case "list-ingresses": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get ingresses ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No ingresses found" }]
      };
    }
  • Schema definition for the list-ingresses tool, specifying the optional namespace parameter.
    {
      name: "list-ingresses",
      description: "List Kubernetes ingresses in a namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list ingresses from (optional, defaults to current context namespace)"
          }
        }
      }
  • server.js:1392-1394 (registration)
    Registration of the tools list handler, which includes the list-ingresses tool in the returned tools array for tool discovery.
    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 listing ingresses but doesn't describe output format, pagination, permissions required, rate limits, or error conditions. For a Kubernetes tool with potential complexity, this leaves significant gaps in understanding how it behaves.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and front-loads the essential information.

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 Kubernetes listing tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned, how results are formatted, whether authentication is needed, or how it interacts with the Kubernetes context. The description alone doesn't provide enough context for reliable use.

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?

Schema description coverage is 100%, with the single parameter 'namespace' fully documented in the schema. The description doesn't add any parameter semantics beyond what's already in the schema, so it meets the baseline of 3 for high schema coverage without adding value.

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 ingresses in a namespace'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'list-all' or 'list-services', but the specificity of 'ingresses' provides adequate differentiation for most contexts.

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 is provided on when to use this tool versus alternatives like 'list-all' (which might include ingresses) or 'describe-service' (for related resources). The description only states what it does, not when it's appropriate or what prerequisites might exist.

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