Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

ping_host

Check host connectivity and measure latency by sending ICMP packets. Specify the target host and optional packet count to diagnose network reachability.

Instructions

Ping a host to check connectivity and latency

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

Input Schema

NameRequiredDescriptionDefault
hostYesHost to ping
countNoNumber of ping packets to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond intent. It does not say how unreachable hosts or timeouts are reported, whether ICMP privileges are required, or what the response contains (RTT, packet loss).

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?

A single front-loaded sentence with the action and the two measured outcomes; nothing is wasted or buried.

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?

For a simple two-parameter read tool with a fully described schema the description is enough to select it, but without an output schema the agent still cannot anticipate what a successful or failed ping returns, which is the main remaining gap.

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 coverage is 100%, so both 'host' and 'count' (with a default of 4) are already documented in the schema. The description adds no format hints, no guidance on packet-count tradeoffs, and no host syntax (IP vs hostname), so it stays at the baseline for fully documented schemas.

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 (ping) and resource (host) plus the two things it measures, connectivity and latency, so an agent can separate it from dig_dns or whois_lookup. It does not explicitly name the sibling tools it differs from (e.g. traceroute for path analysis), which keeps it below 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?

Usage is implied by 'check connectivity and latency' — a reachability/latency probe. There is no explicit when-not guidance, no mention of what to use instead for path tracing (traceroute) or name resolution (dig_dns), so the agent must infer the boundaries from sibling names.

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