Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_attack_chain

Read-onlyIdempotent

Orders caller-supplied security findings into a reviewable severity-based attack chain to clarify attack paths and prioritize review.

Instructions

Order caller-supplied findings into a reviewable severity-based attack chain.

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": {
      "findings": "<findings>"
    },
    "name": "oc_attack_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
findingsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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, so the safety profile is covered. The description adds that output is severity-ordered and intended for review, which is real behavioral context. It says nothing about how severity is determined (field name? inference from finding content?) or what happens to findings lacking severity data.

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?

One sentence with no filler, and the operative concept (severity-based ordering of supplied findings) is front-loaded. Nothing is redundant, though the brevity comes at the cost of the parameter detail noted above.

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?

Return values are covered by an output schema, so the description needn't explain them. For a low-complexity single-parameter tool this is close to sufficient, but the caller still must guess what constitutes a valid 'finding' object, which matters given the fully untyped array input.

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 coverage is 0% on the single parameter, and the schema only says the findings array contains free-form objects with additionalProperties=true. The description implies findings carry severity information and that ordering is derived from it, which is more than the schema conveys. However, it never states the expected keys or whether a 'severity' field is required, so it only partially compensates for the coverage gap.

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 names a specific verb ('order'), a specific input ('caller-supplied findings'), and a specific output artifact ('severity-based attack chain'), so an agent can tell this is a transform/organize operation rather than a scanner. It does not contrast itself with similarly named siblings such as oc_chain_get or oc_chain_plan, leaving that differentiation to inference.

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 statement of when to use this versus oc_chain_plan or oc_chain_get, no prerequisite (e.g. 'call after collecting findings from scanners'), and no exclusions. The word 'reviewable' hints at a post-collection workflow but usage is entirely implied.

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