Skip to main content
Glama

Topolograph

get_network_by_graph_time

Read-onlyIdempotent

Fetch network data by explicit graph_time.

Description: This tool retrieves network information for a specific graph time. Universal tool that works with both OSPF and IS-IS protocols. Use 'node_id' to find all networks terminated by a specific node. Use 'ip_address' to find which network a specific IP belongs to.

Input fields: graph_time (str): REQUIRED - The specific graph time to query, use the most latest from get_all_graphs to get graph_time. network_w_digit_mask (str, optional): Network with mask (e.g., 10.0.0.0/24). Helpful when needed to find all devices which terminate the network ip_address (str, optional): IP address to find which network it belongs to node_id (str, optional): Universal node identifier to find all networks terminated by this node. Exact match only (no hostname or case-insensitive lookup here). - For OSPF: Use Router ID (e.g., "10.10.10.1") - For IS-IS: Use System ID (e.g., "1921.6800.1001") filter_type (str, optional): all, backuped_only or non_backuped_only; lists the networks of the graph by backup status, not with the three fields above at (str, optional): ISO 8601 moment; state with watcher events applied up to it. Not with the three lookup fields page, per_page (int, optional): page of the list read with filter_type or at; check pagination.total

Output fields: dict: A dictionary containing network information.

Examples: - get_network_by_graph_time("graph123", node_id="10.10.10.1") # All networks terminated by OSPF Router ID - get_network_by_graph_time("graph123", node_id="1921.6800.1001") # All networks terminated by IS-IS System ID - get_network_by_graph_time("graph123", ip_address="192.168.1.5") # Find network for IP 192.168.1.5

Equivalent to GET /network/{graph_time}, or GET /graph/{graph_time}/networks with filter_type or at.

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

Input Schema

NameRequiredDescriptionDefault
atNo
pageNo
node_idNo
per_pageNo
graph_timeYes
ip_addressNo
filter_typeNo
network_w_digit_maskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful operational context beyond them: protocol universality, exact-match-only semantics for node_id (no hostname/case-insensitive lookup), pagination via pagination.total, and REST equivalents. It stops short of describing result shape or any rate/size limits.

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?

The sectioned layout (Description, Input fields, Output fields, Examples, Equivalent) is front-loaded and easy to scan, and examples earn their place. There is minor redundancy in the lead sentence and a weak 'Output fields: dict' line, but nothing that obscures the call contract.

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 an 8-parameter tool with no output schema, the description covers every input, the mode-switching logic, and the REST equivalent, which is sufficient to call it correctly. The only gap is return-value structure, which is reduced to 'a dictionary containing network information' despite there being no output schema to fill that in.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: graph_time is marked REQUIRED with sourcing guidance, node_id documents OSPF Router ID vs IS-IS System ID formats and exact-match behavior, ip_address and network_w_digit_mask have concrete examples, filter_type explains the enum values, and page/per_page point to pagination.total.

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 ('Fetch network data by explicit graph_time', 'retrieves network information for a specific graph time') and scopes it as a universal OSPF/IS-IS tool. It also names the dependency tool get_all_graphs for obtaining graph_time, so the agent can place it relative to siblings.

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 explicit routing rules: node_id finds networks terminated by a node, ip_address finds the network for an IP, filter_type lists by backup status, and at applies watcher state. It also states mutual exclusions ('Not with the three lookup fields', 'not with the three fields above'), which is exactly the when/when-not guidance needed.

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.