Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_engagement_get

Read-onlyIdempotent

Retrieve metadata for a single server-generated OpenCyber engagement ID to confirm workspace details and scope before running authorized security operations.

Instructions

Return metadata for one server-generated OpenCyber engagement 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": {
      "engagement_id": "<engagement_id>"
    },
    "name": "oc_engagement_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds only that the lookup is by a server-generated identifier; it says nothing about behavior for unknown or malformed IDs or entitlement checks.

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 front-loaded sentence with no filler; the scope qualifier ('one', 'server-generated') arrives immediately. It is efficient, though one more clause on ID provenance or failure behavior would have been worth its length.

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?

The tool is simple (one required string) and has an output schema plus rich annotations, so most burden is lifted. The description is adequate but does not close the remaining gap on where the ID comes from or what happens on a bad ID.

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?

The single parameter has 0% schema description coverage, so the description must carry meaning — and it partially does by specifying the ID is 'server-generated', clarifying provenance and expected format origin. It does not state whether the ID is a UUID, an integer-like string, or how to obtain it (presumably oc_engagement_create).

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: 'Return metadata for one ... engagement ID.' The word 'one' implicitly contrasts with the list-style sibling, so an agent can tell this is the single-record fetch. It does not name a sibling explicitly, keeping it short of a 5.

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?

Usage is only implied: fetch by a known ID. The adjective 'server-generated' hints that the ID must originate from creation rather than being chosen by the caller, which is a useful precondition. There is no explicit when-to-use vs. oc_engagement_list or when-not guidance.

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