Skip to main content
Glama

ont_help

Discover which CLI commands exist under a given ONT path before making changes. Read-only exploration appends '?' to inspect top-level or nested command options safely.

Instructions

Ask the ONT's own CLI what commands exist under a path: '' for the top level, 'show', 'config', 'config wan' and so on. Read-only: it only appends '?'. Use it to explore before running a change.

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": "ont_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoCommand path; empty for top level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it declares the operation read-only and explains the mechanism ('it only appends ?'), which reassures the agent nothing is mutated. It stops short of describing the shape of the response (text vs structured command list), which is the main remaining gap.

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

Conciseness5/5

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

Two tight sentences with the purpose and the path convention front-loaded, followed by the safety note and usage hint. No redundant or filler wording.

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-optional-parameter, no-output-schema discovery tool, the description covers purpose, path syntax, safety, and usage. Only the return format is left implicit, which is a minor omission given how simple the tool is.

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?

Schema coverage is 100%, so baseline would be 3, but the description goes beyond it by giving concrete path examples ('', 'show', 'config', 'config wan'), clarifying the hierarchical path syntax and that empty string means top level.

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: query the ONT's own CLI for the commands that exist under a given path. The phrase 'Use it to explore before running a change' implicitly distinguishes it from the mutating sibling ont_run, so an agent can tell discovery apart from execution without opening a 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 a clear when-to-use: explore before making a change, i.e. read the command tree first. It does not explicitly name ont_run or state when not to use this tool, but the sequencing guidance is unambiguous enough to route the agent.

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