Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_result_get

Read-onlyIdempotent

Retrieve a specific retained tool result by evidence_id; reports digest-only availability when full content is not retained.

Instructions

Read one retained tool result by its evidence_id. Retention is controlled by OPENCYBER_RESULT_RETENTION: off keeps nothing, digest (default) keeps an index entry, and full keeps the redacted payload. When only the digest exists, the response says so instead of pretending content is missing.

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>",
      "evidence_id": "<evidence_id>"
    },
    "name": "oc_result_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidence_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value by disclosing the OPENCYBER_RESULT_RETENTION modes and the digest-only fallback, telling the agent to expect an explicit 'content not retained' signal rather than a silent empty result. It omits any auth or scoping requirements.

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?

Three tight sentences with the core action front-loaded; the retention detail is dense but each sentence carries information an agent needs. Slightly heavy on configuration narrative for a read tool.

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?

An output schema exists, so return values need not be explained, and the description covers the key failure mode (digest-only). The main gap is the unexplained engagement_id and the unstated relationship to oc_result_list for obtaining the evidence_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?

Schema description coverage is 0%, so the description must compensate. It clarifies that evidence_id identifies a retained tool result, but says nothing about engagement_id, leaving half the required parameters undocumented in both schema and description.

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: 'Read one retained tool result by its evidence_id.' That is precise enough for an agent to distinguish it from the list-style sibling oc_result_list, though it never names that sibling explicitly.

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 – an agent must infer it should call this after obtaining an evidence_id (presumably from oc_result_list). No explicit when-to-use, when-not-to-use, or alternative is stated.

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