Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_evidence_export

Export explicitly selected engagement files to a sensitive tar.gz evidence bundle with per-file hashes, metadata, and a verified audit snapshot; retain the archive hash.

Instructions

Export explicitly selected engagement files to a sensitive tar.gz evidence bundle with per-file hashes, engagement metadata and a verified audit snapshot. Session credentials are not automatically included; retain the returned archive hash independently.

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>",
      "paths": "<paths>"
    },
    "name": "oc_evidence_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
output_pathNo
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
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), and the description adds genuinely new operational facts: the bundle is sensitive and contains hashes and an audit snapshot, credentials are excluded, and the caller must retain the returned archive hash independently. That last point is exactly the kind of post-call obligation annotations cannot express. It does not say what happens to a pre-existing output file or whether repeated exports produce differing archives.

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?

Two tightly written sentences with the artifact and sensitivity front-loaded and the credential/retention caveat following. No filler, though the second sentence packs two distinct cautions that could be clearer if separated.

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 output schema exists, so return values and the archive hash need no explanation here, and the sensitive-artifact warning is well covered. The gap is on the input side: with zero schema coverage, an agent still has no description of engagement_id or of output_path's default and destination behavior for a non-idempotent write tool.

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% across three parameters, so the description must carry the semantics and largely does not. "Explicitly selected files" loosely maps to paths, but engagement_id and especially output_path (optional, defaults to null — where does the archive go then?) are unexplained.

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?

"Export explicitly selected engagement files to a sensitive tar.gz evidence bundle" gives a concrete verb, resource, and output artifact, plus the bundle's contents (per-file hashes, engagement metadata, verified audit snapshot). It does not name the sibling oc_evidence_verify, which is the natural follow-up for re-checking the archive, so it stops 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?

"Explicitly selected" implies this is for a deliberate, curated set of files rather than a bulk sweep, and the note about session credentials signals a caution to check before sharing. There is no explicit guidance on when to choose this over oc_evidence_verify or oc_poc_evidence, nor any stated prerequisites for an 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