Skip to main content
Glama

Get services

get_services
Read-only

Fetch service summary rows: name, namespace, type, cluster IP, external IPs, ports, selector, and the load balancer addresses of a LoadBalancer service (one still waiting for an address sorts first). A list needs namespace or all_namespaces=true and carries total, returned, truncated and scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific service name to fetch.
namespaceNoKubernetes namespace to list. A list needs either this or all_namespaces=true; a named read (name) needs neither.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
all_namespacesNoSet true to list every namespace on the cluster deliberately. Omit it and pass namespace to list one namespace; a list with neither is refused (error_code scope_required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description goes further by disclosing the returned fields, the ordering quirk (a LoadBalancer still awaiting an address sorts first), and the list envelope keys total/returned/truncated/scope. With no output schema present, that return-shape disclosure is the most valuable part of the text. It stops short of explaining pagination limits or the exact conditions under which truncation triggers.

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?

Two sentences, front-loaded with what is fetched and followed by the list-scoping rule; every clause carries information (field list, sort behaviour, envelope keys). No filler, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, four-parameter tool with no output schema, the description supplies both the payload shape and the mandatory listing scope, which is what an agent needs to call it correctly. Minor gaps remain around truncation thresholds and whether any label/field selector exists, but nothing essential for a correct invocation is missing.

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 coverage is 100%, and the schema already documents the namespace/all_namespaces rule and the scope_required error, so the description's restatement adds no new meaning. It also does not clarify the semantics of 'name' versus 'namespace' interaction (a named read needs neither) beyond what the parameter descriptions say. Baseline 3 applies.

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 opens with a specific verb and resource ('Fetch service summary rows') and enumerates exactly what comes back (name, namespace, type, cluster IP, external IPs, ports, selector, LB addresses), which is far more informative than the bare title. It does not explicitly contrast itself with adjacent readers such as get_pods or get_ingresses, so sibling routing is left to the agent's inference from the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent learns that a list call requires namespace or all_namespaces=true, which is a calling constraint, not guidance about when to prefer this tool over alternatives. There is no mention of when-not to use it, nor of related tools like describe_resource or ssh_kubectl_read for deeper inspection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.