Skip to main content
Glama
imjdl

Nmap MCP Server

list-all-scans

Retrieve and display all stored network scan results to review previous security assessments and analyze network configurations.

Instructions

List all available scan results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic within the call_tool function that executes the 'list-all-scans' tool by iterating over stored scan_results and formatting a list of available scans.
    elif name == "list-all-scans":
        if not scan_results:
            return [
                types.TextContent(
                    type="text",
                    text="No scans have been performed yet.",
                )
            ]
            
        scan_list = []
        for scan_id, scan_data in scan_results.items():
            hosts_count = len(scan_data.get("hosts", []))
            scan_list.append(f"- Scan ID: {scan_id}")
            scan_list.append(f"  Target: {scan_data.get('target')}")
            scan_list.append(f"  Options: {scan_data.get('options')}")
            scan_list.append(f"  Hosts: {hosts_count}")
            scan_list.append("")
            
        return [
            types.TextContent(
                type="text",
                text="Available scans:\n\n" + "\n".join(scan_list),
            )
        ]
  • Registration of the 'list-all-scans' tool in the list_tools decorator, including its description and empty input schema.
    types.Tool(
        name="list-all-scans",
        description="List all available scan results",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    )
  • Input schema definition for the 'list-all-scans' tool, which requires no properties (empty object).
    types.Tool(
        name="list-all-scans",
        description="List all available scan results",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    )
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 but only states the action without details on permissions, rate limits, pagination, or response format. It doesn't clarify if this lists historical scans, real-time results, or includes metadata, leaving significant gaps in understanding how the tool behaves.

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 any fluff or redundancy. It's front-loaded and wastes no words, making it easy for an agent to parse quickly.

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?

For a tool with no annotations, no output schema, and sibling tools, the description is incomplete. It doesn't address behavioral traits like safety, performance, or how results are returned, nor does it help differentiate from alternatives, leaving the agent with insufficient context for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is appropriate given the schema's completeness, warranting a baseline score above minimum viable due to the lack of parameters to explain.

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 verb ('List') and resource ('all available scan results'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-scan-details' or 'run-nmap-scan' beyond the basic listing action, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-scan-details' for specific scan details or 'run-nmap-scan' to initiate new scans. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage from tool names alone.

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/imjdl/nmap-mcpserver'

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