Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

nmap_scan

Scan a target IP or hostname for open ports and services. Specify ports, ranges, or scan types to identify network exposure and running software.

Instructions

Run an nmap port scan on a target IP or hostname. Can scan specific ports or ranges.

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": {
      "target": "<target>"
    },
    "name": "nmap_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNoPorts to scan (e.g., '80,443' or '1-1000')1-1000
targetYesTarget IP address or hostname to scan
scan_typeNoScan type: 'fast', 'full', 'version', 'os'fast

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 burden and largely drops it. It says nothing about scan duration, network intrusiveness/detectability, whether elevated privileges are needed (notably for os/version detection), or what a result looks like. For an active network scan these are material traits an agent should know before invoking.

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?

Two short sentences with the action front-loaded and no filler. The second sentence is close to redundant with the ports parameter description, but it is not costly.

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?

With no annotations and no output schema, the description should compensate for the missing behavior and return-value context, but it does not. An agent gets no sense of runtime, privilege requirements, or result shape (e.g., list of open ports), leaving meaningful gaps for a scanning tool.

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 100%, so the schema already explains target, ports, and scan_type. The description's mention of ports/ranges mirrors the schema without adding syntax, defaults, or meaning for the scan_type enum-like values.

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 states a specific verb and resource ('Run an nmap port scan on a target IP or hostname') plus scope ('specific ports or ranges'), which distinguishes it from sibling scanners like nikto_scan or sqlmap_scan by technique. It stops short of explicitly contrasting with host_discovery or ssl_scan, which an agent might otherwise consider.

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?

'Can scan specific ports or ranges' describes capability, not when-to-use guidance. Nothing tells the agent when to pick this over host_discovery or ssl_scan, nor how the 'fast'/'full'/'version'/'os' scan types should be chosen for a given goal.

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