Skip to main content
Glama

Topolograph

get_nodes

Read-onlyIdempotent

Get a paginated list of nodes/routers from a graph.

Description: Returns structured node data including hostname, system ID, network count, areas, IS-IS flag, and node_attributes (role flags). Supports pre-filtering by protocol, watcher origin, area, and node role flag before returning results. Note: 'network count' is the number of prefixes/networks on a node, NOT its neighbor/adjacency count. To count neighbors per router, use get_edges and count edges per src_node; do not derive neighbor counts from this tool. protocol="bgp" answers "which leaves carry VNI/VRF X" (vni/vrf/rt) and "which routers are BGP speakers" -- rows then carry can_build_path instead of the IGP node fields above.

Input fields: graph_time (str): The graph time identifier, or the name of your OSPF/IS-IS watcher (Enterprise) to read its newest snapshot with events up to now; the answer then names that snapshot in graph_time protocol (str, optional): Filter: only return if graph matches protocol (ospf, ospfv3, isis, yaml, bgp) watcher (bool, optional): Filter: true for watcher-uploaded graphs, false for manually parsed area (str, optional): Filter: only return if graph contains this area (e.g. "0", "0.0.0.1", "49.0001") abr (bool, optional): OSPF role filter — true returns only Area Border Routers (false: only non-ABRs) asbr (bool, optional): OSPF role filter — true returns only AS Boundary Routers (false: only non-ASBRs) overload (bool, optional): IS-IS filter — true returns only routers with the overload (OL) bit set attached (bool, optional): IS-IS filter — true returns only routers with the attached (ATT) bit set maxmetric (bool, optional): OSPF filter — true returns only routers in max-metric (RFC 3137 stub router) state vni (int, optional): protocol="bgp" only -- keep the routers that are a VTEP for this L2VNI vrf (str, optional): protocol="bgp" only -- keep the routers that are a VTEP for this VRF's L3VNI rt (str, optional): protocol="bgp" only -- keep the routers whose resolved RIB view carries this route target page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50) at (str, optional): ISO 8601 moment; state with watcher events applied up to it

Output fields: dict with keys: items: list of nodes with node_id (canonical graph name), display_name (human-readable text), hostname, systemid, networks_count, areas, is_isis, node_attributes (role flags: {"abr":1,"asbr":0,"maxmetric":0} for OSPF, {"overload":1,"attached":0} for IS-IS) pagination: page, per_page, total, total_pages

Equivalent to GET /graph/{graph_time}/nodes.

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": {
      "graph_time": "<graph_time>"
    },
    "name": "get_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
rtNo
abrNo
vniNo
vrfNo
areaNo
asbrNo
pageNo
watcherNo
attachedNo
overloadNo
per_pageNo
protocolNo
maxmetricNo
graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior beyond them: rows change shape under protocol="bgp" (can_build_path replaces IGP node fields), watcher-time reads resolve to the newest snapshot and echo it back in graph_time, and 'network count' is defined as prefix count, not adjacency count.

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?

Well front-loaded and sectioned (behavior notes, then per-parameter semantics, then output). The 'Output fields' block duplicates the supplied output schema and the leading 'Description:' label restates the header, so a small amount of text does not earn its place.

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 15-parameter read tool with no schema descriptions, it covers required vs optional usage, filter polarity, protocol-specific row shapes, pagination defaults, and watcher snapshot semantics. An agent can call this correctly without opening the schema.

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?

With 0% schema description coverage, the description must carry the full burden and it largely does: every one of the 15 params is explained, including protocol's allowed values, area examples ('0', '0.0.0.1', '49.0001'), the true/false polarity of each role filter, and pagination defaults. Minor gap: the interaction between 'at' and 'graph_time' is only implied.

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?

Opens with a specific verb+resource+scope: 'Get a paginated list of nodes/routers from a graph,' then enumerates exactly what each row contains (hostname, system ID, network count, areas, IS-IS flag, node_attributes). It also explicitly distinguishes itself from get_edges by warning not to derive neighbor counts here.

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 an explicit when-not ('To count neighbors per router, use get_edges and count edges per src_node; do not derive neighbor counts from this tool') and names the question each mode answers (protocol="bgp" answers 'which leaves carry VNI/VRF X'). It also clarifies the Enterprise watcher-name shorthand for graph_time.

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.