Skip to main content
Glama

ont_show

Read read-only status and settings from a fibre ONT, such as WAN, LAN, DHCP, ARP and routes. Use it to inspect device state before making changes.

Instructions

Read status or settings from the fibre ONT with 'show '. Read-only, safe. Common items: status (uptime, firmware, WAN), wan, interface, lan, dhcp, arp, route, remoteaccess, portforward, tr069. Call ont_help with path 'show' to list every item this ONT offers.

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": {
      "item": "<item>"
    },
    "name": "ont_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesWhat to show, e.g. 'status'. Extra words are passed through, e.g. 'interface eth0'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety profile on its own and does so explicitly: 'Read-only, safe.' It also discloses the pass-through behaviour of extra tokens. It does not say what happens when an item is unsupported or what the output looks like, which keeps it from a 5.

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?

Three sentences, front-loaded with the action, then the item catalogue, then the discovery route. The item list is long but each entry is a usable value, so it earns its space; nothing is padded or repeated.

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 one-parameter read tool with no output schema and no annotations, this covers what to pass, safety, and how to discover valid values. The one remaining gap is what the response contains (raw CLI text vs structured fields), which matters because no output schema exists.

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 coverage is 100% and the single parameter is documented, so the baseline is 3. The description adds value by enumerating eleven common item values and confirming token pass-through, but the schema already shows the pass-through example, so this is an increment rather than a rewrite.

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: read status or settings from the fibre ONT via 'show <item>'. It contrasts with the write path only implicitly by asserting 'Read-only, safe', and it routes to ont_help for enumeration, so an agent can separate it from a general command runner without opening the schema.

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 concrete usage: pass an item name, extra words are passed through, and call ont_help with path 'show' when the item list needs to be discovered. It stops short of saying when NOT to use it (e.g. instead of ont_run for configuration changes), but the read-only framing supplies that context implicitly.

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

Deploy Server

Other Tools