Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_amass

Destructive

Runs amass for attack-surface and DNS enumeration using supplied argv tokens within an OpenCyber engagement namespace; use relative paths for engagement artifacts.

Instructions

Run amass from the OpenCyber enumeration toolkit. The container executes amass 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_amass"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructive=true, openWorld=true, readOnly=false and idempotent=false, so the risk profile is carried by structured data. The description adds genuinely useful behavior beyond that: raw argv tokens with no shell parsing, engagement-namespace execution, and relative artifact paths. It still does not disclose rate limits, network reach, or what destructive effects to expect, which is a notable gap given destructiveHint=true.

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 compact sentences, front-loaded with the verb and target, followed by the two execution constraints that actually matter. No filler, though the argv sentence and the namespace sentence could be merged for tighter structure.

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 pass-through CLI wrapper nature is conveyed. Still missing for a destructive, open-world enumeration tool: what amass will actually be doing, any network/rate implications, and documentation of the `stdin` parameter.

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 implicitly explains `arguments` (argv tokens, no shell parsing), `engagement_id` (selected engagement namespace), and `working_directory` (relative paths for artifacts), but leaves `stdin` completely undocumented and gives no format or example for the argv array.

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 `amass` from the OpenCyber enumeration toolkit, so it is distinguishable from siblings that wrap other tools by name. However, it never explains what amass does (subdomain/OSINT enumeration) or what class of output to expect, so an agent unfamiliar with amass gets a name but not a purpose.

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?

Usage context is limited to execution semantics: runs in the selected engagement namespace and relative paths should be used for engagement artifacts. There is no explicit when-to-use, when-not-to-use, or pointer to any alternative approach for enumeration, so the agent must infer the call conditions.

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