Skip to main content
Glama

Topolograph

get_lsps

Read-onlyIdempotent

List MPLS TE LSP tunnels, or get one tunnel by name.

Description: Each returned path already carries its last CSPF placement outcome: placed (bool), reason (human-readable explanation, null when placed), reason_code (machine-readable failure category, null when placed), binding_constraints (which constraints actually block it), cost (total path metric, null when unplaced).

Act on reason_code, not on the wording of reason:
  disconnected -- no path exists even with every constraint lifted;
    the topology is severed and must be repaired.
  constraints_unsatisfiable -- a path DOES exist, but the request is
    too strict. Do not tell the user connectivity is broken; tell them
    which of binding_constraints to relax (bandwidth, affinity, srlg).
    More than one entry means they block only in combination, so
    relaxing just one will fail again.
  ero_strict_hop_unreachable -- a strict ERO hop has no direct edge.
  endpoint_not_found -- src or dst is not in the graph.

Getting a single tunnel by lsp_name always
includes each path's expanded node-name path; the list form omits it
by default (include_path=True to get it there too, since it can be
large across many tunnels).

Input fields: graph_time (str): The graph time identifier lsp_name (str, optional): Get one tunnel by name instead of listing all status (str, optional): "placed" or "unplaced" -- keep only paths matching via_node (str, optional): Keep only paths whose CSPF-computed path visits this node (e.g. "which tunnels cross router X", pre-maintenance impact check) via_edge (str, optional): "srcNode,dstNode" -- keep only paths traversing this hop via_edge_key (str, optional): Exact stable edge_key (from get_edges(include=["edge_key"])) -- disambiguates parallel/ECMP edges that via_edge alone cannot include_path (bool, optional): Also return each path's expanded node-name path in the list form

Equivalent to GET /graph/{graph_time}/lsps[/{lsp_name}].

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

Input Schema

NameRequiredDescriptionDefault
statusNo
lsp_nameNo
via_edgeNo
via_nodeNo
graph_timeYes
include_pathNo
via_edge_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered; the description goes further by disclosing the per-path CSPF outcome fields and, more importantly, how to act on each reason_code (e.g. constraints_unsatisfiable means a path exists and binding_constraints should be relaxed, not reported as an outage). That is genuinely actionable behavioral context an agent cannot get from the schema. It stops short of discussing payload size limits or pagination for large listings.

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 structure is front-loaded and scannable: purpose, then outcome-field semantics, then an indented reason_code decision list, then an input-field block. Minor redundancy exists ('null when placed' is stated twice on adjacent lines) and the indented reason_code block is verbose, but nearly every line carries operational value.

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 a seven-parameter, read-only query tool with an output schema, the definition covers purpose, every parameter, the difference in returned content between the two modes, and the raw REST equivalent. The remaining gap is operational: nothing says what happens when a listing is very large beyond the include_path warning, so an agent gets no signal about result-size management.

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 all parameter meaning, and it does: all seven fields are documented with type, optionality, and semantics, including concrete formats like 'srcNode,dstNode' for via_edge and the provenance of via_edge_key from get_edges(include=["edge_key"]). The status values are enumerated in prose ('placed' or 'unplaced') even though the schema has no enum.

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?

The opening line states a specific verb and resource plus two modes: 'List MPLS TE LSP tunnels, or get one tunnel by name.' The single-vs-list distinction is sharpened later by noting that the lsp_name form always expands node-name paths while the list form omits them. What's missing is explicit differentiation from siblings such as get_cspf_path or get_path_tree, which plausibly overlap on per-tunnel path inspection.

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?

Usage context is supplied inline for the important filters: via_node is framed as 'which tunnels cross router X, pre-maintenance impact check', and via_edge_key is explicitly positioned as the disambiguator when via_edge cannot separate parallel/ECMP edges. include_path has a stated use condition (large payload across many tunnels). There are no explicit when-not-to-use statements or named sibling alternatives, keeping it below a 5.

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.