Skip to main content
Glama

quick_scan

Scan common TCP ports on an authorized target to identify open services; configure the number of top ports checked (default 100, max 1000).

Instructions

Scan the N most common TCP ports (default 100, max 1000) on a target.

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": "quick_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
top_portsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 behavioral burden. It does disclose the scan's bounded nature (top N ports, default 100, hard max 1000), which is useful context, but says nothing about authorization requirements, network intrusiveness, or rate/timeout behavior for an active network probe.

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 tightly written sentence with no filler, and the scope constraints are placed inline where the agent needs them. 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?

An output schema exists, so return values need not be explained, and the core scope is covered. However, for an active network scanning tool with zero annotations and undocumented parameters, the description is thinner than the risk profile warrants.

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% with only bare titles. The description partially compensates by giving the default (100) and a max cap (1000) for top_ports, which the schema does not state, but it adds nothing about the required target parameter's accepted formats.

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: scanning the N most common TCP ports against a target, with scope limits (default 100, max 1000). This is clearly narrower than a full port_scan, though the description never names or contrasts any sibling tool.

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 when-to-use guidance at all. With siblings like port_scan, service_scan, and vuln_scan present, the agent gets no explicit signal that quick_scan is the lightweight reconnaissance option rather than a substitute for a full or service-aware scan.

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