Skip to main content
Glama

Get node usage

get_node_usage
Read-only

Live CPU and memory usage per node, measured by metrics-server right now (the twin of ankra cluster top nodes), with each node's allocatable capacity and the percentage in use. 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 prove resource pressure before scaling; get_cluster_status only gives cluster-wide percentages. 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_node_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return (default 25).
sort_byNoOrder the rows by CPU (default) or memory, highest first.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it declares that results are never cached and always freshly measured, and it names the two concrete failure modes (agent unreachable, metrics-server not installed). That is exactly the operational context an agent needs before relying on the numbers.

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?

Effectively front-loaded: what it measures, freshness, failure modes, then when to use it. Nearly every clause carries information, though the trailing 'Read-only.' duplicates the readOnlyHint annotation and is dead weight.

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?

With no output schema, the description still conveys the row contents, ordering, and error conditions, which covers most of what an agent needs. Minor remaining gap is that it doesn't state the row envelope or how failures surface, but on balance it is complete for a four-parameter read tool.

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 limit, sort_by, cluster_id and cluster_name are already documented in the schema. The description adds no syntax, defaults, or cluster-selection behavior beyond what the schema states, so the baseline 3 applies.

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 verb and resource ('Live CPU and memory usage per node'), names the measurement source (metrics-server), and lists exactly what each row contains (allocatable capacity, percentage in use). It also anchors to a known CLI equivalent and distinguishes the scope from the cluster-wide sibling, so the agent can pick it without opening the 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?

Gives explicit when-to-use guidance ('prove resource pressure before scaling') and an exclusion against get_cluster_status, which only returns cluster-wide percentages. It does not differentiate against near neighbors like get_pod_usage or get_nodes, which would be the other plausible confusion points, so it stops just short of full routing guidance.

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.