Skip to main content
Glama

verify_audit_chain

Verify the cryptographic integrity of the immutable audit trail by checking the SHA-256 hash chain. Ensures audit data is trustworthy for compliance and dispute resolution.

Instructions

Verify the cryptographic integrity of AVP's immutable audit trail.

Checks that no audit entries have been tampered with by verifying
the SHA-256 hash chain from genesis to the latest entry.

Use this before relying on audit data for compliance or dispute resolution.
For an individual agent's audit history, use get_audit_trail instead.

Read-only — no authentication required. Safe to call at any time.

Returns:
    JSON with is_valid (true/false), total_entries count, latest_hash,
    and verification timestamp. is_valid=false means tampering detected.
    Returns {"error": "..."} on network errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: read-only, no authentication required, safe to call anytime. It explains what the tool checks (SHA-256 hash chain) and describes return values including possible error cases.

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?

The description is concise, well-structured, and front-loaded. Each sentence adds value, covering purpose, mechanism, usage, safety, and return format without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool with an output schema, the description is complete. It explains the return values and error handling, and covers behavioral context. No gaps remain.

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?

The input schema has zero parameters and 100% coverage, so the description needs to add no param info. Baseline is 3, and the description does not add param semantics beyond the schema.

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?

The description clearly states the tool's purpose: verifying cryptographic integrity of the audit trail using SHA-256. It distinguishes from the sibling tool 'get_audit_trail' by noting the difference in scope (entire chain vs. individual agent history).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises use before relying on audit data for compliance or dispute resolution. Also provides an alternative: use 'get_audit_trail' for individual agent audit history.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentveil-protocol/avp-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server