Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_audit_verify

Read-onlyIdempotent

Recompute an engagement audit hash chain to detect tampering and report the first removed, reordered, or edited event.

Instructions

Recompute the engagement audit hash chain and report the first removed, reordered, or edited event.

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

Input Schema

NameRequiredDescriptionDefault
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's marginal contribution is small. It does add one genuinely useful behavioral detail: the check short-circuits and reports only the FIRST anomaly, which matters for interpreting partial results, but it says nothing about cost versus chain length or behavior on a clean 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?

One sentence, front-loaded with the action and ending on the outcome; no filler or restatement of the name.

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?

A one-parameter read-only tool with a rich annotation set and an output schema, so return-value explanation is unnecessary. The only real gap is the absence of any statement about what a successful verify (intact chain) yields versus a failure.

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% for the single engagement_id parameter, so the description must compensate and only partially does: 'the engagement audit hash chain' implies the ID scopes the check to one engagement. It gives no format, validation, or error expectations for that parameter.

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 object ('Recompute the engagement audit hash chain') plus a concrete outcome ('report the first removed, reordered, or edited event'), which is enough to separate it from evidence or plain audit-log tools. It stops short of naming a sibling alternative, so it lands at clear-but-undifferentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance and no stated prerequisites. The verb 'verify/recompute' implies its role as the integrity-check counterpart to an audit log, but an agent must infer that on its own.

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