Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_engagement_create

Creates a persistent engagement namespace for authorized security work and returns its server-generated ID, scoping targets and objective for tracking.

Instructions

Create a persistent engagement namespace and return its server-generated ID.

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": {
      "name": "<name>",
      "targets": "<targets>"
    },
    "name": "oc_engagement_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
targetsYes
objectiveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: the namespace is persistent and the ID is server-generated, implying the ID is not supplied by the caller. It does not say what happens on a duplicate name, whether target strings must resolve to real assets, or whether the call can partially fail mid-creation.

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?

A single tight sentence with the action front-loaded and zero filler. It is efficient, though for a 3-parameter mutation tool with no schema documentation it is arguably undersized rather than wasteful.

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 spelled out, but everything else is missing: no parameter meaning, no usage context, no failure or validation behavior. For a creation tool with non-idempotent, non-readonly semantics and 0% schema coverage, the description leaves too much for the agent to guess.

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%, so all three parameters (name, targets, objective) are undocumented in structured fields and the description must compensate. It explains none of them: it does not say whether 'name' must be unique, what format 'targets' entries take (host, CIDR, domain), or what 'objective' is for and what the empty-default means.

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?

States a specific verb and resource: 'Create a persistent engagement namespace', plus the return value (server-generated ID). It is clearly distinct from read-side siblings like oc_engagement_get and oc_engagement_list, though the description itself never names or contrasts those alternatives.

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 call this versus oc_engagement_get, oc_engagement_list, or oc_engagement_plan, and no stated preconditions. The agent must infer from the tool name alone that this is the entry point for starting a new 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