Skip to main content
Glama

list_scans

List recent nmap scans, optionally filtered by target, with newest results first so you can review or diff prior scan history.

Instructions

List recent scans, optionally filtered by target, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does convey two useful traits: this is a read-only listing operation and results are ordered newest first. It omits how many results come back by default, whether older scans beyond the "recent" window are excluded, and what "recent" means in practice.

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?

A single front-loaded sentence with no filler: purpose, optional filter, and ordering all in one clause. Nothing repeats the name or title and no sentence is wasted.

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 simple two-parameter list tool with an output schema, the essentials are covered. The gaps that remain — what limit controls, its default, and what "recent" bounds — are the ones an agent would most plausibly get wrong when paginating or expecting a full history.

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 0%, so the description must compensate. It clarifies that target is an optional filter on the listing, which adds real meaning, but the limit parameter and its default of 20 are never mentioned, leaving half the inputs undocumented anywhere.

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 gives a specific verb and resource ("List recent scans") plus an ordering guarantee ("newest first"), so the agent knows exactly what is returned. It does not explicitly contrast itself with get_scan or diff_latest, so sibling differentiation is left to inference 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?

"Optionally filtered by target" implies when to use the filter, which is a reasonable usage hint. However, there is no explicit statement of when to prefer this over get_scan (single scan retrieval) or diff_scans, and no guidance on when a broad unfiltered listing is appropriate.

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