Skip to main content
Glama

get_verify_receipt_batch

Read-only

Use when an auditor or compliance agent needs programmatic batch verification of governed settlement receipts. Accepts receipt IDs or pasted receipt JSON; returns per-item three-layer trust verdicts (post-quantum signature, digest binding, on-chain anchor) with zero persistence. Read and verify only — no re-issuance. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
receiptsNo
receipt_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds material context beyond them: zero persistence, no re-issuance, the exact composition of the returned verdict, and a $0.10 USDC per-call cost. Cost and persistence characteristics are precisely the operational facts annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the usage trigger, then inputs/outputs, then scope and cost caveats. No filler, though the per-item output detail is denser than strictly needed to select the tool.

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?

No output schema exists, so the description's account of per-item three-layer verdicts is doing necessary work, and billing plus persistence guarantees are disclosed. For a two-parameter, non-destructive verification tool, an agent has what it needs to invoke it correctly.

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?

With 0% schema description coverage, the description must carry the parameters, and it does identify the two input modes as receipt IDs or pasted receipt JSON. It does not say whether they are mutually exclusive, whether both may be combined, or any batch-size limit, so the mapping to the two array properties remains partly inferential.

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?

States a specific verb and resource — batch verification of governed settlement receipts — and scopes it to auditors/compliance agents. The three-layer verdict output (post-quantum signature, digest binding, on-chain anchor) makes it unmistakable from the data-retrieval siblings.

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

Usage Guidelines4/5

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

'Use when an auditor or compliance agent needs programmatic batch verification' gives a concrete trigger, and 'Read and verify only — no re-issuance' rules out the adjacent action an agent might assume. No alternatives are named, but the sibling list contains no comparable verification tool, so there is little to route between.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources