Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_uro

Destructive

Executes uro with supplied arguments in an isolated engagement workspace to deduplicate and filter discovered URLs for focused web reconnaissance.

Instructions

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

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

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond that: argv tokens are passed directly with no shell parsing, and execution is scoped to the engagement namespace with relative artifact paths. It still omits what the run mutates or produces (e.g. whether output files are written to the namespace).

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 action and immediately followed by the execution model. No filler or repetition.

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 described, and the execution contract is reasonably covered. However, for a destructive, non-idempotent process wrapper with 0% parameter coverage, the definition should explain the tool's actual function and stdin behavior to be callable with confidence.

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 4 parameters, so the description must carry the load. It explains that 'arguments' are raw argv tokens (no shell parsing) and that 'working_directory' should be relative to the engagement namespace, but 'stdin' is never mentioned and 'engagement_id' is only implied by 'selected engagement namespace'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ('Run') and specific binary ('uro'), but never states what uro does (URL deduplication / filtering for recon output). An agent unfamiliar with the tool learns only that it executes a subprocess; nothing distinguishes its purpose from the dozens of other oc_* 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?

No when-to-use guidance, no prerequisites, no alternatives. 'Runs from the selected engagement namespace; use relative paths for engagement artifacts' is execution scoping, not invocation guidance, so the agent gets no signal on when this tool beats a sibling.

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