Skip to main content
Glama

istio-list-virtualservices

List Istio virtual services in a Kubernetes namespace to manage traffic routing rules and service mesh configurations.

Instructions

List Istio virtual services

Input Schema

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

Implementation Reference

  • Handler that lists Istio VirtualServices by executing 'kubectl get virtualservices -o wide' in the specified namespace.
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl get virtualservices ${nsArg} -o wide`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No Istio virtual services found" }]
      };
    }
  • server.js:1288-1298 (registration)
    Tool registration in the tools array, including name, description, and input schema for 'istio-list-virtualservices'.
    name: "istio-list-virtualservices",
    description: "List Istio virtual services",
    inputSchema: {
      type: "object",
      properties: {
        namespace: { 
          type: "string",
          description: "The namespace to list virtual services from (optional, defaults to current context namespace)"
        }
      }
    }
  • Input schema definition for the istio-list-virtualservices tool.
    type: "object",
    properties: {
      namespace: { 
        type: "string",
        description: "The namespace to list virtual services 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. It only states the action ('List') without details on permissions required, output format, pagination, error handling, or rate limits. For a tool with no annotation coverage, this is insufficient to inform safe and effective use.

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, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning full marks for brevity and clarity.

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 likely returns a list of virtual services. It doesn't explain what information is returned, how results are formatted, or any behavioral nuances, leaving significant gaps for the agent to operate 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 'namespace' parameter well-documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating 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 verb ('List') and resource ('Istio virtual services'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'istio-list-gateways' or 'list-all', which could also list resources, so it doesn't fully distinguish itself from alternatives.

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 like 'istio-list-gateways' or 'list-all'. It lacks context about prerequisites, exclusions, or specific scenarios where this tool is preferred, leaving the agent to infer usage from the name alone.

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