Skip to main content
Glama

vuln_scan

Run Nmap vulnerability-detection scripts against an authorized target, defaulting to safe-tagged scripts only; set NMAP_ALLOW_INTRUSIVE=1 to enable the full vuln category.

Instructions

Run vulnerability-detection scripts: safe-tagged only, or full vuln category if NMAP_ALLOW_INTRUSIVE=1.

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": {
      "target": "<target>"
    },
    "name": "vuln_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNo
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the safe-vs-intrusive gating via an environment variable, but says nothing about permissions required, whether output is destructive to the target, or how the environment variable is set/checked by the caller.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the safety condition attached immediately, no filler. It is arguably too terse rather than bloated, but nothing 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?

The output schema covers return values, so its absence from the description is acceptable. However, for a potentially intrusive scan tool with zero annotation coverage and undocumented parameters, the definition leaves key operational details for the agent to guess.

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 for two undocumented parameters. It never mentions 'target' or 'ports', and gives no format hints (e.g. port list syntax or that an empty ports value means a default range).

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 and resource: runs vulnerability-detection scripts against a target. It is distinguishable from auditing siblings by the 'vuln' category focus, though it never explicitly contrasts itself with script_scan or port_scan.

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?

Gives a meaningful usage condition — safe-tagged scripts by default, full vuln category only when NMAP_ALLOW_INTRUSIVE=1 — which tells the agent when intrusive behavior is available. It offers no guidance on when to pick this tool over the many sibling scan tools.

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