Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_dirsearch

Destructive

Run web directory and file discovery scans in an isolated engagement workspace, passing raw arguments directly without shell parsing.

Instructions

Run dirsearch from the OpenCyber web toolkit. The container executes dirsearch 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_dirsearch"
  }
}

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, so the risk profile is known. The description adds genuinely new execution semantics: argv tokens are passed directly with no shell parsing, which tells the agent that pipes, redirects, and globbing will not work and that quoting must be handled as separate tokens. It does not describe output or what a scan may alter on the target.

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 what runs, followed by the execution model and the path scoping rule. Every sentence carries information; no filler or repetition of the name.

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?

For a 4-parameter wrapper with rich annotations and an output schema, the description covers the essentials an agent needs to invoke it correctly: the binary, the argv execution model, and the working-directory convention. The remaining gap is the undocumented `stdin` parameter and the absence of guidance on when this tool beats its siblings.

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 the most misuse-prone parameter by explaining that `arguments` is an argv token list with no shell parsing, and it ties the run to the engagement namespace and relative working paths. It says nothing about `stdin`, which remains undocumented in both schema and description.

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 dirsearch from the OpenCyber web toolkit.' That is unambiguous about what executes. It does not, however, contrast itself with the many other scanning siblings, so the agent must already know that dirsearch is a web content-discovery tool.

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?

Provides one concrete operational guideline — run against the selected engagement namespace and use relative paths for engagement artifacts — but never states when to prefer this over alternative scanners or any exclusions/preconditions. Usage is implied by the tool name rather than explained.

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