Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_masscan

Destructive

Executes port scans with supplied command-line arguments in an isolated engagement workspace, avoiding shell parsing for authorized network reconnaissance.

Instructions

Run masscan from the OpenCyber network toolkit. The container executes masscan directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

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": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_masscan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotency, so the safety posture is covered. The description adds meaningful behavior beyond that: argv are passed literally with no shell interpretation, execution is scoped to the selected engagement namespace, and artifact paths must be relative. It omits scanning rate/impact expectations, but the key execution contract is disclosed.

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?

Three short sentences, front-loaded with the action, then the execution contract, then path scoping. Almost no waste; only the 'OpenCyber network toolkit' phrase borders on filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-value explanation is unnecessary. For a passthrough binary-execution tool with four parameters, the description covers the critical contract (argv semantics, no shell, namespace, relative paths); only stdin handling and target/rate expectations are unaddressed.

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 description must compensate. It clarifies that 'arguments' is a token array passed to masscan without shell parsing, that 'working_directory' selects a relative engagement path, and that 'engagement_id' roots execution in a namespace, but leaves 'stdin' unexplained and gives no argv format examples.

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?

The description names a specific verb and resource ('Run masscan') and clarifies the execution model: the container invokes the binary directly with argv tokens and no shell parsing. That distinguishes it from a generic shell tool, but it never says it is not a substitute for other scanners or what masscan does relative to sibling wrapper tools.

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?

Operational guidance exists for the working directory ('use relative paths for engagement artifacts') and the engagement namespace, but there is no when-to-use guidance, no exclusions, and no pointer to alternative tools.

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

Deploy Server

Other Tools