Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_paramspider

Destructive

Discovers URL parameters from archived web data by executing supplied arguments within an isolated engagement workspace, without shell parsing.

Instructions

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

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.1/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 and idempotentHint=false, so the safety profile is carried structurally. The description adds genuinely new behavioral context: argv tokens are passed without shell parsing (no shell injection or wildcard expansion), execution is scoped to the engagement namespace, and paths should be relative to engagement artifacts. It stops short of saying what the run mutates or writes, which is what the destructive flag would benefit from most.

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 and then the execution semantics; nothing is redundant. It is efficient, though it spends its space on mechanics while leaving the tool's actual purpose unstated.

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 annotation set covers mutability and openness. However, for a destructive command-wrapper with four undocumented parameters, the description leaves out what the underlying tool does, how `stdin` is consumed, and what side effects to expect in the engagement workspace.

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, and it partly does: it explains that `arguments` are raw argv tokens with no shell interpretation, that execution is tied to the engagement namespace implied by `engagement_id`, and that artifact paths should be relative, which speaks to `working_directory`. `stdin` is never mentioned and no format/example of typical argv tokens is given.

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?

The description names a specific verb and resource (run `paramspider` from the OpenCyber web toolkit), but it never states what paramspider actually does or what output to expect, so an agent unfamiliar with the binary gets only a name. It also gives no differentiation from the very similar sibling `oc_arjun`, which probes for URL parameters too.

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?

There is no guidance on when to choose this tool over alternatives such as oc_arjun, and no preconditions or exclusions. The only usage-like notes are operational (engagement namespace scoping, relative paths), which help execution but not tool selection.

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