Skip to main content
Glama

nav2_ready

Run a Nav2 pre-flight check that verifies all required servers are active and data streams are alive before navigation, returning ok only when readiness passes.

Instructions

Pre-flight check for Nav2: ok is true only if every server is active and the streams are alive.

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

Input Schema

NameRequiredDescriptionDefault
nsNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the exact truth condition for "ok", which is genuinely valuable. However, it never says whether the call blocks, how long it waits, what happens on timeout, or what permissions/topics it needs, so significant behavioral questions remain unanswered.

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?

A single tight sentence with the purpose front-loaded and the success semantics immediately after; no filler. It is arguably slightly too terse given the unaddressed parameters, but every word present earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations, no output schema, and three undocumented parameters mean the description must do more than one sentence. It hints at an "ok" return field but omits the timeout/blocking semantics of "seconds" and the scope effects of "ns"/"domain_id", leaving real gaps for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% and the description explains none of the three parameters. The meanings of "ns", "domain_id", and especially "seconds" (presumably a wait/timeout window that changes the tool's blocking behavior) must be guessed, so the description does not compensate for the undocumented schema.

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?

"Pre-flight check for Nav2" plus a concrete success condition ("ok is true only if every server is active and the streams are alive") tells an agent exactly what the tool verifies and what the result means. It is clearly distinct from a diagnosis tool by framing itself as a readiness gate, though it never names diagnose_nav2 to make the distinction explicit.

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

Usage Guidelines3/5

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

"Pre-flight check" implies a timing convention (run before launching/using Nav2), which is useful but only implied. There is no statement of when NOT to use it or which sibling to reach for when the check fails, leaving the agent to infer the escalation path.

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