Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_chain_get

Read-onlyIdempotent

Retrieve a persisted CVE capability chain by chain ID, or list chain summaries with verdict, step count, and creation time when no ID is provided.

Instructions

Read one persisted CVE capability chain by chain_id, or list chain summaries (verdict, step count, created_at) when chain_id is omitted.

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_chain_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
chain_idNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing mode-dependent behavior and the shape of list-mode results (verdict, step count, created_at), though it says nothing about behavior when chain_id does not resolve to a chain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the primary read case front-loaded and the fallback list mode immediately after. No filler, no restatement of the tool name, and the parenthetical preview of summary fields is compact and informative.

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?

With annotations covering safety and an output schema covering return structure, the description only needs to explain the two modes and what they yield, which it does. The remaining gap is the unexplained required engagement_id and the lack of any not-found/error behavior, which matters for a lookup tool.

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?

Schema description coverage is 0%, so the description must carry the semantics, and it only half does. It explains chain_id well (default empty string means list mode), but engagement_id — a required parameter — is never mentioned, leaving the scoping of the lookup undefined in prose.

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 gives a specific verb ('Read') plus resource ('persisted CVE capability chain') and cleanly separates two modes: single-chain fetch by chain_id versus a summary listing. It implicitly distinguishes itself from the planning sibling by emphasizing 'persisted', but never names an alternative explicitly, so it stops just short of full sibling differentiation.

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?

It clearly states the trigger for list mode ('when chain_id is omitted'), which is genuine usage guidance. However, it gives no guidance on when to call this versus oc_chain_plan or oc_attack_chain, nor any prerequisites such as whether the chain must already exist in the given 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