Skip to main content
Glama

traceroute

Read-onlyIdempotent

Trace the network path to a host and show delay at each hop to identify where traffic slows or stops.

Instructions

Trace the network path to one host and show the delay at each hop, to find where traffic slows down or stops. max_hops: 1-30 (default 15). Takes up to a minute or two.

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_hopsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two things the annotations do not: an expected duration ('up to a minute or two'), which matters for an agent sequencing calls, and the hop-limit range. It doesn't mention firewall/ICMP-blocking behavior, which would be the natural next detail for a network trace.

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?

Three short sentences, purpose front-loaded, constraint and runtime trailing. Nothing is redundant and every clause carries information the schema and annotations don't.

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?

An output schema exists, so return values need no explanation, and the duration plus hop range cover the operational essentials for an agent. Minor gaps: host format expectations and what happens when hops time out or the target blocks ICMP.

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%, so the description must compensate — and it partially does by giving the max_hops bounds (1-30) and default (15), which the schema only shows as a bare default 15. The 'host' parameter is left as just 'one host' with no format hint (IP vs hostname vs URL).

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 definition opens with a specific verb+resource ('Trace the network path to one host') and adds the observable output ('delay at each hop'), which cleanly separates it from ping/dns_lookup/check_port by behavior. It does not name a sibling explicitly, so it stops short of a 5.

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?

The stated goal ('to find where traffic slows down or stops') implies the diagnostic scenario where this tool is the right pick, but there is no explicit when-not guidance or pointer to the cheaper alternatives (ping, dns_lookup) for cases where path detail isn't needed. Usage is inferable rather than stated.

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