Skip to main content
Glama

tools_masscan

Scan large IP ranges for open ports with high-speed SYN packets. Masscan asynchronously probes targets at configurable rates for efficient network reconnaissance.

Instructions

Execute Masscan for fast port scanning across large IP ranges.

Masscan is an internet-scale port scanner capable of scanning the entire internet in under 6 minutes. It produces SYN packets asynchronously, making it significantly faster than traditional scanners for large target ranges.

Args: target: Target IP, CIDR range, or hostname (e.g., '10.0.0.0/24') ports: Port specification (default: '1-65535' for full range). Supports ranges ('1-1024'), lists ('80,443,8080'), or mixed ('22,80,443,8000-9000'). rate: Packets per second (default: 1000). Higher values scan faster but may overwhelm the network or trigger IDS. Common values: 1000 (safe), 10000 (moderate), 100000 (aggressive). additional_args: Extra masscan arguments (e.g., '--banners' to grab service banners)

Example usage: tools_masscan(target='192.168.1.0/24', ports='80,443,8080', rate=5000) tools_masscan(target='10.0.0.1', ports='1-1024') tools_masscan(target='172.16.0.0/16', ports='22,80,443', rate=10000, additional_args='--banners')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNo
portsNo1-65535
targetYes
additional_argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: Masscan is fast, uses asynchronous SYN packets, and high rates may overwhelm networks or trigger IDS. However, it does not mention required permissions, whether the tool is read-only, or potential destructive effects beyond network load. The description is adequate but leaves gaps.

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?

The description is concise with a brief intro, structured arg list, and three practical examples. Every sentence adds value, no redundancy, and it is optimally front-loaded with the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers usage, parameters, and examples well. However, it does not describe the tool's return value or output format, even though an output schema exists. Given the tool's complexity, this is a minor gap, but overall it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are absent (0% coverage), but the tool description provides thorough explanations for all four parameters: target (format), ports (ranges/lists/mixed), rate (values and impact), and additional_args (examples like --banners). This fully compensates for the schema gap, adding significant meaning beyond basic types and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool executes Masscan for fast port scanning across large IP ranges. It clearly differentiates Masscan from other scanners like Nmap by highlighting its speed and capability to scan the entire internet. The purpose is unambiguous and well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (fast port scanning over large ranges) and includes example invocations. However, it does not explicitly state when not to use it or directly compare to sibling tools like tools_nmap, though the context is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zebbern/zebbern-kali-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server