Skip to main content
Glama

istio-list-gateways

List Istio gateways in a Kubernetes namespace to manage network traffic routing and service mesh configuration.

Instructions

List Istio gateways

Input Schema

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

Implementation Reference

  • Handler for the istio-list-gateways tool. Parses input arguments for namespace, runs 'kubectl get gateways -o wide' (with optional namespace), and returns the command output or a fallback message.
    case "istio-list-gateways": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get gateways ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No Istio gateways found" }]
      };
    }
  • server.js:1301-1312 (registration)
    Tool registration in the tools array used by ListToolsRequestHandler. Defines the tool name, description, and input schema (optional namespace parameter).
      name: "istio-list-gateways",
      description: "List Istio gateways",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list gateways from (optional, defaults to current context namespace)"
          }
        }
      }
    },
  • Input schema definition for istio-list-gateways tool, specifying an optional 'namespace' string parameter.
      name: "istio-list-gateways",
      description: "List Istio gateways",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list gateways from (optional, defaults to current context namespace)"
          }
        }
      }
    },
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. While 'List' implies a read-only operation, the description doesn't mention any behavioral traits such as permission requirements, rate limits, output format, or pagination behavior. This leaves significant gaps for a tool that interacts with a cluster resource.

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 extremely concise with just three words, front-loading the essential information ('List Istio gateways') without any wasted text. Every word earns its place, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a tool that lists cluster resources. It doesn't cover behavioral aspects like output format, error handling, or authentication needs, which are crucial for an agent to use the tool effectively in a Kubernetes/Istio context.

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 single parameter 'namespace' fully documented in the schema itself. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score 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 ('Istio gateways'), making the purpose immediately understandable. However, it doesn't differentiate itself from sibling tools like 'istio-list-virtualservices' or general listing tools like 'list-all', which would require explicit comparison to achieve a perfect score.

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. With many sibling listing tools available (e.g., 'istio-list-virtualservices', 'list-all', 'list-services'), the description offers no context about specific use cases, prerequisites, or comparisons to help an agent choose appropriately.

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