Skip to main content
Glama
mohdhaji87

Nmap MCP Server

by mohdhaji87

nmap_ping_scan

Discover live hosts on a network by performing ping scans to identify active devices before conducting detailed network analysis.

Instructions

Perform ping scan to discover live hosts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYes
ping_typeNoboth

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:221-224 (registration)
    Registers the 'nmap_ping_scan' tool using the FastMCP @app.tool decorator, specifying its name and description.
    @app.tool(
        name="nmap_ping_scan",
        description="Perform ping scan to discover live hosts"
    )
  • The main handler function for the 'nmap_ping_scan' tool. It constructs Nmap arguments based on the ping_type parameter (icmp, tcp, or both), executes the scan using the shared run_nmap_command helper, and returns the formatted results or error message.
    async def nmap_ping_scan(
        targets: str,
        ping_type: str = "both"
    ) -> str:
        """Perform ping scan to discover live hosts."""
        if ping_type == "icmp":
            args = ["-sn", targets]
        elif ping_type == "tcp":
            args = ["-PS", targets]
        else:  # both
            args = ["-sn", "-PS", targets]
        
        result = run_nmap_command(args)
        
        if result["success"]:
            return f"Ping scan completed:\n\n{result['stdout']}"
        else:
            return f"Ping scan failed:\n\n{result['stderr']}"
  • Shared utility function used by nmap_ping_scan (and other tools) to execute Nmap commands via subprocess, handling output, errors, timeouts, and providing structured results.
    def run_nmap_command(args: List[str], timeout: int = 300) -> Dict[str, Any]:
        """
        Execute an nmap command and return the results.
        
        Args:
            args: List of nmap command arguments
            timeout: Command timeout in seconds
        
        Returns:
            Dictionary containing command output, error, and exit code
        """
        try:
            # Construct the full nmap command
            cmd = ["nmap"] + args
            
            logger.info(f"Executing nmap command: {' '.join(cmd)}")
            
            # Run the command with timeout
            result = subprocess.run(
                cmd,
                capture_output=True,
                text=True,
                timeout=timeout,
                check=False
            )
            
            return {
                "stdout": result.stdout,
                "stderr": result.stderr,
                "exit_code": result.returncode,
                "success": result.returncode == 0
            }
            
        except subprocess.TimeoutExpired:
            return {
                "stdout": "",
                "stderr": f"Command timed out after {timeout} seconds",
                "exit_code": -1,
                "success": False
            }
        except FileNotFoundError:
            return {
                "stdout": "",
                "stderr": "nmap command not found. Please ensure nmap is installed and in PATH",
                "exit_code": -1,
                "success": False
            }
        except Exception as e:
            return {
                "stdout": "",
                "stderr": f"Error executing nmap command: {str(e)}",
                "exit_code": -1,
                "success": False
            }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool performs a ping scan to discover live hosts, but lacks details on permissions needed, network impact, rate limits, output format (though output schema exists), or whether it's read-only or destructive. This is inadequate for a network scanning tool.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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?

Given the complexity of network scanning, no annotations, and 0% schema description coverage, the description is insufficient. It doesn't explain parameter usage, behavioral traits, or when to use it versus siblings. The existence of an output schema helps with return values, but other critical context is missing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds no information about the 'targets' or 'ping_type' parameters beyond what the schema provides (just their names). No context on target format (e.g., IP ranges, hostnames) or ping type options (e.g., ICMP, TCP) is given.

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 clearly states the action ('Perform ping scan') and the goal ('to discover live hosts'), which is specific and distinguishes it from siblings focused on port scanning, OS detection, or vulnerability scanning. However, it doesn't explicitly differentiate from 'nmap_network_discovery' which might have overlapping functionality.

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?

No guidance is provided on when to use this tool versus alternatives like 'nmap_network_discovery' or other sibling tools. The description only states what it does, not when it's appropriate or what scenarios it's best suited for.

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/mohdhaji87/Nmap-MCP-Server'

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