Skip to main content
Glama

get_scan

Retrieve the full stored result of a previously run nmap scan by its scan ID to review findings or compare past audit results.

Instructions

Retrieve the full stored result for a previously run scan by its id.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idYes

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?

No annotations are supplied, so the description carries the full burden. It does disclose one meaningful trait – the result is persisted output from a prior run, not a live scan – which distinguishes it from the scanning siblings. However, it says nothing about permissions, side effects, or behavior for stale/missing scan ids.

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?

One sentence, front-loaded with the verb and resource, with zero redundant wording.

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?

An output schema exists, so return values need no explanation, and one integer parameter is low complexity. The remaining gap is the missing acquisition path for scan_id and error behavior, which matters for an id-keyed lookup 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 coverage is 0% and the single parameter has no description in the schema. The phrase 'by its id' ties the argument to the tool's purpose but adds no format, source, or validation detail beyond the parameter name 'scan_id'.

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?

States a specific verb ('Retrieve') and resource ('full stored result for a previously run scan') qualified 'by its id'. The word 'stored' and 'previously run' implicitly separates it from the scan-executing siblings (port_scan, quick_scan, vuln_scan), though no sibling is named explicitly.

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?

'previously run scan' implies a scan must exist before calling, but the description never says where to obtain a scan_id (e.g., list_scans) or what happens when the id is unknown. Usage is implied rather than directed.

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