Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

traceroute

Trace the network path to a target host to identify intermediate routers and diagnose connectivity or routing issues.

Instructions

Trace the network path to a host

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
hostYesTarget host

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say which protocol is used (ICMP/UDP/TCP), whether elevated privileges are needed, whether the call blocks for many seconds, or what the output looks like (hop list, RTTs).

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?

One short, front-loaded clause with zero filler. It is efficient, though the terseness is also the source of the missing behavioral detail rather than a virtue in itself.

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?

The tool is structurally simple, but with no annotations and no output schema, the description is the only source of behavioral information and it provides none. An agent cannot tell whether this is a fast or long-running call, what it returns, or what permissions it needs before invoking it.

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?

There is a single required parameter and schema coverage is 100%, so the schema already documents 'host' adequately. The phrase 'to a host' adds no format detail such as hostname vs IP or IPv6 support, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Trace the network path to a host'. An agent can distinguish this from a DNS resolver or port scanner by the notion of hop-by-hop path tracing, though it never names which sibling it is not.

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?

There is no guidance on when to choose this over ping_host, nmap_scan, or host_discovery. The description states what the tool does but leaves the agent to infer that it is for path/latency diagnosis rather than reachability checks or service enumeration.

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