Skip to main content
Glama

port_scan

Scan specified TCP or UDP ports on an authorized target to identify open services, choosing syn, connect, or udp scan types for targeted network checks.

Instructions

Scan specific TCP/UDP ports on a target; scan_type is one of syn, connect, udp.

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>",
      "ports": "<ports>"
    },
    "name": "port_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsYes
targetYes
scan_typeNosyn

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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, yet it discloses nothing about authorization/scope requirements, intrusiveness or detection risk, timing, or whether the scan is connection-heavy. It only names the scan modes, which is closer to parameter semantics than operational behavior.

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 clause with no filler; the scan_type enumeration is attached immediately where it is needed. It is terse to the point of under-specification rather than being verbose, so no trimming is warranted, only additions.

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?

An output schema exists, so return values need not be explained, but for a 3-parameter active network scanner with zero annotation coverage the definition is too thin. Missing authorization caveats and the syntax of both required parameters are things an agent needs to invoke this safely and correctly.

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 schema offers only bare string types and titles. The description rescues the most consequential gap by enumerating scan_type values (syn, connect, udp) that the schema lacks as an enum, but leaves both required parameters (target format, ports syntax such as ranges vs comma lists) undocumented.

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 ("Scan specific TCP/UDP ports on a target") and narrows scope with "specific ports," which implicitly sets it apart from broad sweep tools like quick_scan or discover_hosts. It stops short of naming or contrasting any sibling explicitly, so the differentiator from service_scan or script_scan must be inferred.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as target authorization or scope, and no pointer to alternatives like service_scan for version detection. The phrase "specific TCP/UDP ports" is a scoping statement rather than routing guidance.

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