Skip to main content
Glama

Traceroute

traceroute
Read-only

Trace the network path to a hostname or IPv4 address with ICMP probes and return hop-by-hop results, while letting you set the source interface, source IPv4 address, and maximum hops.

Instructions

Trace the network path to a hostname or IPv4 address using ICMP probes. Supports selecting the source interface, source IPv4 address, and maximum number of hops (default: 30). Returns the collected hop-by-hop traceroute output.

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

Input Schema

NameRequiredDescriptionDefault
hostYes
max_hopsNoMaximum number of traceroute hops (1-64, default: 30).
source_addressNoIPv4 address to use as the source address for traceroute.
source_interfaceNoAny existing Keenetic interface name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

The description adds crucial behavioral traits beyond the annotations, specifying that it uses ICMP probes and defines the default value for the maximum number of hops (30).

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?

The definition is highly concise and efficient, front-loading the core function and mechanism in the first sentence without unnecessary fluff.

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?

It is largely complete, covering the function, mechanism, defaults, and output type. However, it does not specify the format or content of the hop-by-hop output.

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?

Since schema coverage is only 75%, the description helps by explicitly stating that it supports selecting the source interface, source address, and maximum hops, identifying them as configuration options.

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?

The tool clearly defines its function: tracing the network path to a hostname or IPv4 address using ICMP probes, distinguishing it from simple ping operations.

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 description fails to provide guidance on when to use this tool versus alternatives (like using a specific interface vs. relying on the default), offering only operational details.

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