Skip to main content
Glama

traceroute

Read-only

Maps the network path from a MikroTik router to an IPv4 or IPv6 host, showing hops and probe timing to diagnose routing and connectivity issues.

Instructions

Traces the route from the router to an IPv4/IPv6 address or host name (needs the "test" policy).

Notes: count: probes per hop; the run takes roughly count x hops x timeout at worst. timeout: per-probe timeout, e.g. "500ms" or "1s". port applies to protocol="udp".

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": {
      "address": "<address>"
    },
    "name": "traceroute"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
sizeNo
countNo
deviceNo
addressYes
timeoutNo
use_dnsNo
max_hopsNo
protocolNoicmp
interfaceNo
src_addressNo
routing_tableNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is known. The description adds genuine context beyond that: a device-side policy prerequisite and a runtime cost formula that warns of long runs. It does not explain truncation on timeout, per-hop failure behavior, or what happens when the target is unreachable.

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 core sentence is front-loaded and the follow-up notes are short and non-redundant. Minor structural flaw: the 'port applies to protocol="udp"' clause is nested under the timeout note rather than standing on its own, which slightly obscures it.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the policy and cost caveats cover the main operational risk. For a 12-parameter tool with zero schema descriptions, though, the omission of routing_table, interface, src_address, and max_hops meaning leaves the agent guessing on most of the surface.

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 0% across 12 parameters, so the description must carry the semantics. It explains count (probes per hop), timeout (format examples '500ms'/'1s'), and clarifies that port applies only to protocol="udp" — but leaves max_hops, size, protocol, interface, src_address, routing_table, use_dns, and device entirely uninterpreted.

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 description gives a specific verb and resource ('Traces the route from the router to an IPv4/IPv6 address or host name') and names the required 'test' policy, so the agent knows exactly what the operation does. It stops short of naming a sibling such as check_route_path to contrast active probing with route-table inspection, so differentiation is implicit rather than 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?

It states a prerequisite ('needs the "test" policy') and provides cost-model guidance ('the run takes roughly count x hops x timeout at worst'), which implies caution on large runs. However, there is no explicit when-to-use versus when-not-to-use statement or reference to an alternative tool for route diagnostics.

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