Skip to main content
Glama

read_transaction_record_evidence

Read-only

Read operation terms, receipts and complaint statements, or protected candidate and replica proofs. Wallet must be the buyer or original seller. Snapshot is unsigned; private bodies and reusable payment authorizations are excluded.

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context beyond that: an authorization constraint (buyer or original seller), the fact that the returned 'snapshot is unsigned' (i.e., not cryptographically attested), and explicit exclusions ('private bodies and reusable payment authorizations are excluded'). These are exactly the caveats an agent needs to avoid over-trusting the output. It stops short of explaining pagination or what an unsigned snapshot means operationally.

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 short sentences, front-loaded with what is readable, then the authorization gate, then the caveats. No filler. 'Snapshot is unsigned' is terse to the point of being cryptic but occupies minimal space.

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

Completeness2/5

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

The schema uses an allOf/oneOf discriminator over three `kind` values with format-dependent `id`, plus required `challengeId` and `signature`, and there is no output schema to describe the return. For that complexity, the description omits the challenge-then-sign flow and the parameter contract entirely, leaving the agent unable to construct a valid call from the description alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and largely fails: neither `signature` (a 0x-prefixed 130-hex value) nor `challengeId` is mentioned at all, and the agent gets no hint that a challenge must be obtained from create_transaction_record_evidence_challenge first. The `kind`/`id` coupling (UUID for `operation`, 0x hash for the protected kinds) is only obliquely implied by the list of readable resources. With four required parameters, this is a significant gap.

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

Purpose4/5

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

The description opens with a specific verb and enumerated resource types (operation terms, receipts, complaint statements, protected candidate/replica proofs), which maps onto the `kind` enum values in the schema. It distinguishes this read from the merchant/assigned variants only implicitly by naming the resource family. Jargon like 'protected candidate and replica proofs' is unclear without more grounding, but an agent can still tell this is a signed read of evidence records.

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 precondition 'Wallet must be the buyer or original seller' is genuine selection guidance, telling the agent who is allowed to call it. However, there is no when-to-use-vs-alternative statement despite siblings like read_transaction_evidence, read_merchant_transaction_evidence, and read_assigned_operation_evidence that clearly overlap. The agent must infer which reader to pick from the resource wording alone.

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