Skip to main content
Glama

Get pod usage

get_pod_usage
Read-only

Live CPU and memory usage per pod, measured by metrics-server right now (the twin of ankra cluster top pods), summed over the pod's containers, optionally with the per-container breakdown. Filter to one namespace or read every namespace. Never answered from a cache, so a result is always a fresh measurement; fails when the agent is unreachable or metrics-server is not installed. Use this to find what is actually consuming a node; get_pods shows requests and limits, not usage. Read-only.

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": "get_pod_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return (default 25).
sort_byNoOrder the rows by CPU (default) or memory, highest first.
namespaceNoOnly pods in this namespace. Omit for every namespace.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
include_containersNoInclude the per-container usage under each pod (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add real value: no caching (always a fresh metrics-server measurement) and explicit failure modes (unreachable agent, metrics-server not installed). It also discloses the data source and container-level summation, though it says nothing about result freshness windows, staleness of metrics-server samples, or pagination beyond the limit param.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool measures, then options, then behavior and failure modes, then the sibling comparison. Dense and largely waste-free, though it packs everything into one long run-on block; the CLI twin parenthetical is marginally useful for mapping but adds length.

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?

For a read-only metrics tool with no output schema and full parameter documentation, the description covers source, aggregation semantics, scoping options, freshness, and failure modes. An agent has everything needed to decide whether to call it and what to expect when it fails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by clarifying that usage is summed over the pod's containers unless include_containers is set, and that omitting namespace reads every namespace. It adds no detail on limit or sort_by, but the schema already documents those fully.

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?

States a specific resource and operation: live per-pod CPU and memory usage from metrics-server, summed across containers, with optional per-container breakdown. It explicitly distinguishes itself from the sibling get_pods ('shows requests and limits, not usage'), so an agent can pick 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 Guidelines5/5

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

Gives the selecting condition clearly ('Use this to find what is actually consuming a node') and names the alternative plus why it is wrong for this purpose (get_pods returns requests/limits, not usage). Also states the namespace filtering choice explicitly: one namespace or all namespaces.

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.