Skip to main content
Glama

Get pods

get_pods
Read-only

Fetch pod information as one summary row per pod: name, namespace, phase, ready (x/y), restarts, node, age and reason (the first container that is not ready, e.g. CrashLoopBackOff or ImagePullBackOff). Not-ready and failed pods sort first. Filter by namespace/name/labels; a list needs namespace or all_namespaces=true and carries total, returned, truncated and scope. Use this to check pod health, find crashing pods, or verify deployments. For logs, use get_pod_logs instead.

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_pods"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific pod name to fetch. If provided, returns only that pod.
limitNoMaximum number of pods to return.
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).
label_selectorNoLabel selector to filter pods (e.g., 'app=nginx,tier=frontend').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses sorting behavior ('Not-ready and failed pods sort first'), the meaning of the 'reason' field with concrete CrashLoopBackOff/ImagePullBackOff examples, the scope-refusal condition for list calls, and the truncation indicators (total, returned, truncated, scope) carried in the response. That is substantive behavioral context the annotations do not provide, and nothing contradicts readOnlyHint=true.

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?

One dense but well-ordered block: output shape first, then sort behavior, then filtering and scope rules, then use cases, then the log alternative. Every sentence carries information and the alternative is correctly placed last as a routing note.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields and the truncation metadata, and it explains the failure mode (scope_required) an agent will hit on an unqualified list call. For a six-parameter read tool with only a readOnlyHint annotation, nothing an agent needs in order to call it correctly 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 description coverage is 100%, so each parameter is already documented, including the namespace/all_namespaces scope rule and the label_selector example. The description's 'filter by namespace/name/labels' framing and the list-scope requirement largely restate what the schema already states, adding only a light cross-parameter summary; limit and cluster_id are not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Fetch pod information') and immediately pins down the output shape: 'one summary row per pod: name, namespace, phase, ready (x/y), restarts, node, age and reason'. It also disambiguates from the nearest sibling by naming get_pod_logs as the tool for log retrieval, so an agent can choose between them without opening either schema.

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

Usage Guidelines4/5

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

It gives concrete when-to-use conditions ('check pod health, find crashing pods, or verify deployments') and one explicit alternative ('For logs, use get_pod_logs instead'). It does not rule out other close siblings such as get_pod_usage or list_security_pods, so the routing is clear but not exhaustive.

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.