Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_httpie

Destructive

Run HTTPie commands directly with supplied argv tokens—no shell parsing—inside an engagement-scoped workspace for authorized HTTP testing.

Instructions

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

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

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

Annotations already flag destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is carried structurally. The description adds one genuinely important behavioral fact — no shell parsing, raw argv execution — but is silent on permissions, network egress, timeouts, and how stdin is consumed.

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 sentences, front-loaded with the action, then the execution model, then the path convention — no wasted clauses. 'from the OpenCyber web toolkit' is mild branding filler, but everything else earns its place.

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?

An output schema exists, so return values need not be described, and the annotations cover safety and openness. What remains thin is guidance on how the tool actually behaves as a CLI wrapper — argument construction conventions and stdin handling — but for a general-purpose command runner the definition is close to sufficient.

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?

With 0% schema description coverage, the description must compensate and it does so only partially: 'arguments' is clarified as literal argv tokens with no shell interpretation, and 'working_directory' is addressed via the relative-path guidance. 'stdin' and the precise role of 'engagement_id' receive no explanation, leaving two of four parameters undocumented.

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 httpie (`http`) inside the OpenCyber container using supplied argv tokens. An agent can immediately tell this is an HTTP-request tool rather than a generic shell, though it never contrasts itself with sibling oc_bash, which is the obvious overlap case.

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?

There is implied and partial guidance — use relative paths for engagement artifacts and operate within the selected engagement namespace — but no explicit when-to-use or when-not-to-use versus alternatives such as oc_bash. The agent must infer that this tool is for HTTPie invocations specifically.

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