Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

host_discovery

Identifies live hosts on a network with an Nmap ping scan from a CIDR range, helping map active IP addresses for reconnaissance.

Instructions

Discover live hosts on a network using nmap ping scan

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": {
      "network": "<network>"
    },
    "name": "host_discovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYesNetwork range in CIDR notation (e.g., 192.168.1.0/24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does add real context by identifying the mechanism as an nmap ping scan — implying a lightweight sweep that does not probe ports. It omits important caveats: whether elevated privileges are needed, expected runtime, and that hosts blocking ICMP may be missed.

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?

One short sentence, front-loaded with the action and resource, with zero redundant or filler wording. Nothing could be removed without losing meaning.

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 one-parameter scanning tool with no annotations and no output schema, the description should still say roughly what comes back (a list of live IPs) and flag the ICMP/permission caveats. It covers the core action adequately but leaves return shape and limitations unaddressed.

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% and the single 'network' parameter already carries a CIDR example, so the schema does the heavy lifting. The description adds no format or scope constraints beyond what the schema states, which is the baseline case for full coverage.

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?

Uses a specific verb ('Discover') plus resource ('live hosts') and names the underlying technique ('nmap ping scan'), which separates it conceptually from a full port scan or a single-host ping. It stops short of naming the sibling tools explicitly, so differentiation is inferable rather than stated.

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 phrase 'discover live hosts on a network' implies a host-enumeration/recon phase, which is enough for an agent to place it in a workflow. However, it never says when to prefer this over nmap_scan or ping_host, and gives no exclusions or prerequisites, so the guidance is only implied.

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