Skip to main content
Glama

net_tools_traceroute

[$x402 pago por llamada] Traceroute real (máx. 20 saltos, 2s de espera por salto, 20s total).

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

Input Schema

NameRequiredDescriptionDefault
hostYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 useful limits (20 hops, 2s per hop, 20s cap) and that the call is billed per invocation via x402. It says nothing about failure behavior, permission/network requirements, or what the trace returns.

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 compact sentence with the resource and its operational limits front-loaded; no filler. The bracketed payment tag is awkwardly placed but still brief.

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 an undocumented required 'host' parameter leave the description doing too little: nothing about expected output shape, error/402 flow beyond the schema, or what a valid target looks like.

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?

Only the x_payment parameter has schema documentation (50% coverage), and the description adds no meaning for 'host' — an agent cannot tell from this text whether it accepts a hostname, IP, or URL. The description does not compensate for the coverage gap.

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?

States a specific verb+resource ('Traceroute real') and adds concrete scope (max 20 hops, 2s per hop, 20s total). It is clearly distinguishable from siblings like net_tools_ping or net_tools_redirect_trace, though it never says what 'real' means versus those tools.

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?

No indication of when to choose traceroute over ping, port_scan, or redirect_trace, nor any prerequisites. The only usage-relevant signal is the bracketed note that each call is paid via x402, which is not framed as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources