Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_execute

Destructive

Dispatch an executable-backed catalog entry by exact oc_* name as a compact-mode fallback; use relative paths for engagement artifacts.

Instructions

Dispatch one executable-backed catalog entry by its exact oc_* name returned by oc_catalog. This is primarily a compact-mode fallback; in full mode prefer the direct named tool. 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": {
      "tool": "<tool>",
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_execute"
  }
}

Input Schema

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

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

Annotations already declare destructive=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the risk profile is largely carried by structured data. The description adds a useful operational convention ("Use relative paths for engagement artifacts") that isn't in the annotations or schema, but it never explains that this runs arbitrary external executables, what the engagement scoping guarantees are, or how stdio/working directory affect execution.

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 with the purpose first, then the mode routing, then the path convention — front-loaded and free of filler. The unexplained "compact-mode" jargon is the only drag on structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 annotations cover the safety profile. But for a five-parameter, zero-coverage, destructive execution dispatcher, the description leaves the argument-passing contract and the meaning of engagement_id almost entirely unspecified, which is not enough to invoke it confidently.

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% across five parameters, and the description only clarifies two of them: `tool` must be an exact `oc_*` name from oc_catalog, and paths should be relative for engagement artifacts (relevant to `working_directory`). Nothing explains `arguments` (presumably argv), `stdin`, or `engagement_id`, so the agent must guess at the shape of the majority of the input.

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 states a specific action ("Dispatch one executable-backed catalog entry") and ties the identifier to its source ("by its exact `oc_*` name returned by oc_catalog"), which cleanly separates it from oc_catalog and from the direct named tools. It loses a point because "compact-mode fallback" is introduced without definition, so the core verb is clear but the framing term is opaque.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing: this is the compact-mode path, and in full mode the agent should prefer the directly named sibling tool. That is a real when-to-use/when-not statement rather than implied usage, though it never says when dispatching through this wrapper is unsafe or how to decide if the named tool exists.

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