Skip to main content
Glama

Get nodes

get_nodes
Read-only

Fetch node information from the cluster. Shows node status, roles, capacity, allocatable resources, conditions, and network addresses (internal_ip, external_ip, hostname). Note: external_ip is only populated when the cloud provider assigns a public IP directly to the node; nodes on a private network behind a bastion/gateway typically expose only an internal_ip. For the SSH jump-host public IP of an Ankra-provisioned cloud cluster, use get_cluster_bastion. The payload carries total, returned, truncated and scope; nodes that are not ready sort first.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific node name to fetch.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only supply readOnlyHint, so the description carries the real behavioral burden and does so well: it discloses truncation semantics (payload carries total, returned, truncated, scope), sort order (not-ready nodes first), and the conditional-fill caveat that external_ip only exists when the cloud provider assigns a public IP directly to the node.

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 the core purpose, then layered with caveats in descending priority. Every sentence contributes, though the external_ip/bastion explanation runs two sentences for what is essentially one routing hint.

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 must describe the response, and it does: field set, truncation envelope, and ordering. The only gap is that truncation is disclosed without any stated way to page past it, and the relationship to list_cluster_nodes remains implicit.

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 both the name and cluster_id parameters are already fully documented in the schema. The description adds no syntax or format guidance for either parameter, so the 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?

States a specific verb and resource ("Fetch node information from the cluster") and enumerates the returned attributes: status, roles, capacity, allocatable resources, conditions, and addresses. An agent knows exactly what data this yields, though the boundary versus the sibling list_cluster_nodes is never addressed.

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 an explicit routing rule to a specific alternative: for the SSH jump-host public IP of an Ankra-provisioned cloud cluster, use get_cluster_bastion. It does not explain when to pass the optional name parameter versus fetching all nodes, nor when to prefer list_cluster_nodes, leaving that inference to the caller.

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.