Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_evidence_verify

Read-onlyIdempotent

Verify an engagement evidence archive without extraction by checking member inventory, file sizes, hashes, and audit snapshot integrity against an optional expected SHA-256.

Instructions

Verify an engagement evidence archive without extraction: exact member inventory, file sizes and hashes, and audit snapshot integrity. Supply an independently retained expected_sha256 for an external comparison point.

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>",
      "path": "<path>"
    },
    "name": "oc_evidence_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
engagement_idYes
expected_sha256No

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, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: the archive is inspected without extraction, the exact checks performed are enumerated, and the hash comparison depends on an externally retained value. It does not say what happens when the hash mismatches or how failures are reported.

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?

Two sentences, front-loaded with the core action and scope, followed by the one non-obvious parameter instruction. No filler or restatement of the title.

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 no explanation, and the description is sufficient to understand the verification semantics and the optional comparison anchor. The main residual gap is the ambiguous meaning of 'path' for a moderately complex verification 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 load. It explains expected_sha256 well ('independently retained', 'external comparison point'), but engagement_id and especially path (archive path vs. output path vs. directory) are left undefined by 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 (verify) on a specific resource (engagement evidence archive) and enumerates what is checked: member inventory, file sizes and hashes, audit snapshot integrity. The phrase 'without extraction' implicitly separates it from oc_evidence_export, but it never names the sibling, so the differentiation is suggestive rather than explicit.

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 context is implied by 'without extraction' and by the instruction to supply an independently retained expected_sha256, which tells the agent how to get an external comparison point. There is no explicit when-to-use versus when-to-use-oc_audit_verify or oc_evidence_export guidance, and no stated prerequisites or exclusions.

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