Skip to main content
Glama
mcp-server-devops
by Feliper83

Kubernetes Pod Status

k8s_pod_status

Lists Kubernetes pod status, including phase, readiness, restarts, and node, optionally filtered by namespace, using live cluster data or mock data when no backend is configured.

Instructions

List pod status (phase, readiness, restarts, node) for a Kubernetes cluster. Connects to a real cluster when KUBECONFIG or MCP_K8S_IN_CLUSTER is set; otherwise returns realistic mock data for a telecom provisioning platform so the tool is demoable without infra.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "k8s_pod_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoRestrict results to this namespace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers the most important disclosure: results may be realistic mock data rather than live cluster state, with the exact environment variables that switch modes. What it leaves out is secondary but real — it never says the operation is strictly read-only, whether output is bounded/paginated, or how connection failures surface.

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, both earning their place: the first defines the output surface, the second defines the data source and its toggle. The most decision-relevant facts are front-loaded and there is no filler.

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 simple read tool with one optional parameter and no output schema, this is close to complete: it names the fields returned and flags the mock-data mode so the agent can caveat results. The only shortfall is the absence of any note on read-only safety or result volume, which matters slightly given there are no annotations to lean on.

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?

There is a single optional parameter whose meaning is fully documented in the schema (100% coverage), so the baseline of 3 applies. The description does not mention the namespace filter at all, adding nothing beyond the structured field, though nothing is lost either.

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 gives a specific verb and resource ('List pod status') and even enumerates the returned fields (phase, readiness, restarts, node), so the agent knows exactly what it gets. It does not, however, position itself against the available siblings (grafana_dashboard_summary, prometheus_query), leaving the reader to infer that pod-level state differs from metric queries.

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?

It states a real precondition for behavior (real cluster when KUBECONFIG or MCP_K8S_IN_CLUSTER is set, mock data otherwise), which is genuinely useful context for interpreting results. But there is no explicit when-to-use guidance versus alternatives such as prometheus_query for metrics, and no statement about when this tool should be avoided.

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