Skip to main content
Glama

Basic Audit Decode

dcl_audit_decode
Read-onlyIdempotent

Retrieve a single audit record from the tamper-evident chain by transaction hash, enabling post-action verification of AI outputs.

Instructions

POST-ACTION Basic Audit ($0.10). Retrieves a record from the tamper-evident chain by tx_hash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tx_hashYesTransaction hash of the audit chain record to retrieve.
payment_idNoOptional payment identifier returned by a previous call when payment is required

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoSet if tx_hash was not found; other fields are omitted.
reasonNoExplanation recorded for the verdict.
tx_hashNoHash of the audit chain record.
verdictNoCOMMIT or NO_COMMIT.
agent_idNoIdentifier of the agent tied to this record.
prev_hashNoHash of the preceding record in the chain.
seal_textNoHuman-readable Leibniz Layer verification seal.
task_typeNoTask type tag recorded with this entry.
timestampNoUnix timestamp when the record was created.
confidenceNoConfidence score recorded for the verdict.
verify_urlNoPublic URL to independently verify this seal.
chain_indexNoSequential index of the record in the chain.
chain_integrityNoTrue if the full chain verifies as intact.
Behavior4/5

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

The description adds helpful behavioral context beyond annotations, including a cost of $0.10 and the tamper-evident nature of the chain. It aligns with the readOnlyHint and idempotentHint annotations, reinforcing that this is a safe, read-only operation. No contradictions with annotations.

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 a single, front-loaded sentence that conveys the tool's purpose, cost, and key identifier with no unnecessary words. It is highly concise and well-structured.

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?

For a simple lookup tool with comprehensive annotations, full schema coverage, and an output schema, the description is adequate. It lacks explicit notes on error handling or payment_id usage, but these are covered by the schema and contextual signals, making the overall package reasonably complete.

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 already provides complete descriptions for both tx_hash and payment_id, achieving 100% coverage. The description adds no additional parameter detail, so the baseline score of 3 is appropriate.

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 states a specific action (retrieves a record) and a specific resource (tamper-evident chain) keyed by tx_hash. The 'Basic' label implicitly distinguishes it from the 'deep' sibling tool, making the purpose unambiguous.

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 description does not explicitly state when to use this tool versus dcl_audit_decode_deep. The term 'Basic' implies a simpler audit, but no clear when/when-not guidance or alternative is provided. The schema's payment_id hint gives minor workflow context, but the description itself lacks usage direction.

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/Fronesis-Labs/dcl-webhook'

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