Skip to main content
Glama

Verify Audit Log

atlas_verify_audit
Read-onlyIdempotent

Verify the audit log's SHA3-256 hash chain and ML-DSA-65 signatures, reporting the first broken entry if tampering or corruption exists.

Instructions

Verify the audit log's SHA3-256 hash chain and ML-DSA-65 signatures. Reports the first broken entry, if any.

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": "atlas_verify_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered; the description adds real value by disclosing the two verification algorithms and the failure-reporting behavior (first broken entry). It does not mention cost or whether the whole log is scanned, which is the main remaining gap for a verification pass.

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 short sentences with zero filler: the verification scope comes first and the result behavior second. Every clause carries information an agent needs.

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 output schema, the description must carry return semantics, and it does so partially — it states that a broken entry is reported, implying a clean pass otherwise, but doesn't say what a successful result contains (e.g., entries verified or head hash). For a zero-parameter check tool this is close to complete, with that one modest gap.

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 there is nothing for the description to disambiguate. Baseline for a parameterless tool applies, with no schema gaps to compensate for.

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?

Names a specific verb (verify), a specific resource (the audit log), and the exact mechanisms checked (SHA3-256 hash chain and ML-DSA-65 signatures). That mechanism-level detail cleanly separates it from siblings like atlas_receipt_status, which concerns status rather than cryptographic integrity.

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 is only implied: an agent can infer it should call this to check audit-log integrity, but the description never states when to prefer it over atlas_receipt_status or atlas_commit_effect, nor any prerequisites or exclusions. No misleading guidance, just absent guidance.

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