Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Port Scan

port_scan

Scans a host for open TCP ports using connect probes, defaulting to common ports, to identify exposed services during authorized reconnaissance.

Instructions

TCP-connect scan a host for open ports (defaults to common ports). [active — needs scope]

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

Input Schema

NameRequiredDescriptionDefault
hostYes
portsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden; it does disclose that this is an active scan requiring scope authorization, which is real behavioral context beyond the schema. It omits rate limits, timeouts, detection risk, and expected duration for a network-scanning tool.

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?

One compact sentence plus a bracketed qualifier; the technique and default behavior are front-loaded. The bracketed tag is slightly cryptic but earns its place by flagging the active/scope constraint.

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 needn't be explained. But for an active scanning tool with zero annotation coverage, the missing scope-check mechanics and port-format guidance leave gaps an agent must guess at.

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%, so the description must compensate, and it only partially does: it clarifies that 'ports' defaults to common ports. It gives no format guidance for the ports array (ranges? list of ints?) and no host format expectations.

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 technique, target, and outcome: 'TCP-connect scan a host for open ports'. This is clearly distinguishable from siblings like http_probe or dns_lookup, though it doesn't explicitly contrast with them.

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?

'[active — needs scope]' implies a prerequisite check (likely scope_status) and flags this as an active probe, which is useful routing signal. However, it doesn't state when to choose this over http_probe or what 'needs scope' operationally means for the agent.

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