Skip to main content
Glama

ospf_interfaces

Read-onlyIdempotent

Inspect OSPF interface settings and diagnose down links or missing adjacencies via mismatched MTU, timers, network type, area, cost, authentication, and neighbor states.

Instructions

Starts with wrong: what is wrong, for OSPF and interfaces, each with a text line (an interface down, an OSPF interface that faces a neighbor and has no adjacency with the values both ends must share and do not, a Full adjacency whose ends still differ); empty when nothing is. Then mismatches and hints (below), then the OSPF interface values per router as collected: MTU, hello and dead intervals, network type, area, cost, DR/BDR role, priority, passive, authentication (none / simple / md5) and neighbor counts. For a link it also gives the other end and mismatches: one line per value that must be equal for an adjacency but is not, e.g. "r1 eth1 MTU 1500 ⇔ r2 eth1 MTU 1400". mismatch_details has the same lines as fields, with odd_end: the router whose value differs from its own other OSPF interfaces while the other end matches its own (an inference, with a note; null when that does not decide it, and for area). A value the router did not report is null and is not compared; each interface also has the neighbor state there, and hints names a link stuck in ExStart / Exchange whose MTU was not reported. All routers, or one with router. 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": "ospf_interfaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoSame input as lab_state (optional here: the server was started with /app/demo/bgp-lp/frameB.json)
routerNoOnly this router, e.g. r1 (default: all routers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Same input as lab_state (optional here: the server was started with /app/demo/compose-bgp-lp/web/xray-states.js)"New value: +"Same input as lab_state (optional here: the server was started with /app/demo/bgp-lp/frameB.json)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / path / description
      Previous value: -"Same input as lab_state"New value: +"Same input as lab_state (optional here: the server was started with /app/demo/compose-bgp-lp/web/xray-states.js)"
    • changedInput schema / required
      Previous value: -[
      -  "path"
      -]New value: +[]
  3. First observedv1.4.3

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, closed-world, and non-destructive. The description adds useful behavior beyond that: unreported values are null and are not compared, `odd_end` is an inference with a `note`, and `hints` covers ExStart/Exchange links with missing MTU data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a long, dense paragraph that is not front-loaded around the tool's purpose. Much of the content is useful output documentation, but it is poorly structured and starts with an awkward clause about `wrong` rather than a clear summary.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly, including `wrong`, `mismatches`, `mismatch_details`, `odd_end`, null handling, neighbor state, and hints. It is less complete on when to choose this tool over siblings, but the output-side completeness is strong for a complex diagnostic 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 the schema already documents both parameters. The description repeats that `router` limits output to one router and that omitting it means all routers, but it adds little beyond the schema and does not explain the `path` parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains the output shape in detail but never states the tool's purpose cleanly up front. It can be inferred that the tool reports OSPF interface values and mismatches, but the opening phrase 'Starts with `wrong`' is output-oriented rather than a clear verb-and-resource statement, and it does not explicitly distinguish itself from ospf_neighbors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage-like guidance is 'All routers, or one with `router`.' There is no explicit guidance on when to use this tool instead of ospf_neighbors, lab_state, or the other siblings, and no stated exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.