Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_engagement_plan

Read-onlyIdempotent

Builds a deterministic OpenCyber engagement plan using catalog tool names for authorized security testing against a specified target and kind.

Instructions

Create a deterministic OpenCyber engagement plan using catalog tool names.

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": {
      "kind": "<kind>",
      "target": "<target>"
    },
    "name": "oc_engagement_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
targetYes
objectiveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, and "deterministic" loosely reinforces idempotency but adds little. The description does not clarify whether a plan is persisted or merely returned (which matters given the readOnlyHint and the existence of oc_engagement_create), nor what inputs drive the plan structure.

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?

It is a single front-loaded sentence with no filler, which is structurally sound. However, the brevity comes at the cost of under-specification rather than efficiency — the one clause that exists ('using catalog tool names') is unexplained.

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 need not be described, but for a three-parameter tool with zero schema coverage the description leaves the caller without parameter meaning or usage conditions. It is not sufficient for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% for all three parameters (kind, target, objective), and the description supplies no meaning for any of them. An agent must guess what values 'kind' and 'target' accept and what the empty-string default for 'objective' implies.

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 verb and resource ("Create ... engagement plan"), but "deterministic" and "using catalog tool names" are cryptic and never explained. It does not differentiate this tool from sibling planners such as oc_chain_plan or oc_hardware_plan, so an agent cannot tell which planner to pick from the description alone.

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 use this planner versus oc_chain_plan, oc_hardware_plan, or oc_engagement_create, and no stated preconditions (e.g., whether an engagement must exist first). The only implied usage is the tool's name itself.

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