Skip to main content
Glama

Verify the audit log is untampered

verify_audit
Read-only

Verifies a tamper-evident audit chain end-to-end by recomputing row hashes and signatures, then reports INTACT or the exact break row to prove the log wasn't edited, reordered, or truncated.

Instructions

Verify the tamper-evident audit chain end-to-end. Recomputes every row's hash and (if signed) signature; reports INTACT, or the exact row where the chain breaks — so you can prove the accountability log wasn't edited, reordered, or truncated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is to add context, and it does: it discloses the cost profile ('recomputes every row'), the conditional handling of signed vs unsigned rows, and the two possible outcomes including failure granularity. What's missing is any note on runtime on large logs or what permissions the chain inspection requires.

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 action and followed by the mechanism and result shape. Every clause carries information an agent needs; nothing is repeated from the title or annotations.

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?

With no parameters and an output schema handling return values, the description covers nearly everything needed to call it correctly, including the conditional signature check. The only gap is operational: no sense of expected duration or behavior on a very large chain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no argument syntax an agent could get wrong. The description correctly frames the call as a full-chain sweep with no scoping options, which implicitly tells the agent it cannot verify a subset.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A precise verb-resource pair ('Verify the tamper-evident audit chain end-to-end') plus the mechanism (recomputing each row's hash and signature) and the outcome (INTACT or the exact breaking row). An agent can distinguish this from a plain log-reading sibling such as audit_log without opening any schema.

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?

The purpose clause ('so you can prove the accountability log wasn't edited') implies when to reach for it — integrity proof after the fact — but there is no explicit when/when-not guidance and no named alternative (e.g., verify_receipt for a single receipt vs this end-to-end sweep). It also doesn't say whether it should be run before acting on log data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.