Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_whatweb

Destructive

Runs web technology fingerprinting scans with supplied arguments in an engagement workspace to identify target web stacks without shell parsing.

Instructions

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

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 readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description earns credit above that baseline by disclosing a real behavioral trait: argv tokens are passed directly and 'shell parsing is never used', which tells the agent that pipes, redirects and shell metacharacters will not work and must be avoided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the operation and with no filler. However, the space is spent on execution mechanics while the more consequential details (argv construction, required engagement_id) are omitted, so the brevity trades off against usefulness.

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 the annotations cover the risk profile. What remains missing is the part only the description could supply: how argv tokens should be shaped, what the required engagement_id selects, and how stdin is consumed — significant gaps for a four-parameter wrapper with zero schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all four parameters, so the description carries the full burden and largely fails. 'Supplied argv tokens' loosely maps to the arguments array and 'relative paths' gestures at working_directory, but engagement_id (required), stdin, and the argv element format are never explained, so an agent cannot know from the description how to construct them.

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?

The description names a specific verb and resource ('Run whatweb from the OpenCyber web toolkit') and makes clear this is a direct wrapper around the whatweb binary. It does not explain what whatweb actually does (web technology fingerprinting), so an agent lacking prior knowledge of the binary gets no functional summary, but the identity of the operation 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 only usage context given is 'Runs from the selected engagement namespace; use relative paths for engagement artifacts', which is a path convention rather than when-to-use guidance. Nothing states when this tool is appropriate versus another recon or shell tool, nor any preconditions on the engagement.

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