Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_arp_scan

Destructive

Run an ARP scan from the selected engagement namespace to discover local network hosts; supply arguments as argv tokens with no shell parsing.

Instructions

Run arp scan from the OpenCyber network toolkit. The container executes arp-scan 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_arp_scan"
  }
}

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
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the risk profile is covered; the description adds genuinely new behavioral context by stating that arp-scan is exec'd directly with argv tokens and that shell parsing is never used, which changes how an agent must format arguments (no quoting, pipes or redirection). It omits that raw-socket privileges are typically required and what partial results look like on failure, keeping it short of a 5.

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, no filler, with the core action front-loaded before the execution-semantics and path notes. The closing path sentence is slightly compressed and would read better if it named the `working_directory` parameter explicitly.

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 described, and annotations cover the safety profile. However, for a destructive, network-facing exec tool the definition should say that targets must be supplied inside `arguments`, note privilege requirements, and explain when stdin is needed — none of which is present.

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% across four parameters, so the description has to carry the meaning, and it partially does: `arguments` is clarified as raw argv tokens with no shell interpretation, and `working_directory` is indirectly covered by the relative-path note tied to the engagement namespace. `stdin` and the exact role of `engagement_id` (beyond namespace selection) are never explained, so compensation is incomplete.

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 ("Run arp scan") and identifies it as part of the OpenCyber network toolkit, so the agent knows exactly what operation is performed. It does not contrast itself with the many adjacent scan siblings (oc_netbios_scan, oc_pcsc_scan, oc_ubertooth_scan), but the tool's identity is unambiguous.

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?

The description gives execution-context guidance ("Runs from the selected engagement namespace; use relative paths for engagement artifacts") but never says when to choose arp scan over the sibling scan tools, nor any prerequisites or exclusions. Usage is only implied by the tool name.

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