Skip to main content
Glama

read_transaction_evidence

Read-only

Read private direct Work Ticket evidence with a buyer-signed read challenge. Includes retained grant/selection/quote/receipt proofs and unsigned server observations, not raw input/results or payment authorizations. Read proofs may be retried until expiry. No on-chain or quality verification.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "challengeId": "<challengeId>",
      "signature": "<signature>",
      "ticketId": "<ticketId>"
    },
    "name": "read_transaction_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that: an auth requirement (buyer-signed read challenge), idempotency/retry semantics ('read proofs may be retried until expiry'), and explicit limits ('no on-chain or quality verification'). It does not say what happens on expiry or failure, which keeps it below a 5.

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, front-loaded sentences with no filler: purpose first, payload scope second, retry and verification caveats last. Dense domain jargon ('grant/selection/quote/receipt proofs') costs a little readability but no sentence is wasted.

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 read-only tool with three required params and no output schema, the description covers payload contents, exclusions, auth, and retry behavior — enough to call it correctly. The main gap is how the challengeId and signature are produced and which sibling generates them.

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. It only obliquely maps to two of three parameters — 'buyer-signed' hints at signature and 'read challenge' at challengeId — and says nothing about ticketId or the 0x-prefixed 130-hex signature format. Most parameter meaning remains undocumented.

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?

States a specific verb and resource ('Read private direct Work Ticket evidence') and enumerates the payload ('retained grant/selection/quote/receipt proofs and unsigned server observations'). The word 'direct' and the explicit exclusions ('not raw input/results or payment authorizations') carve this out from sibling evidence readers, though no sibling is named.

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 implied by prerequisite: a buyer-signed read challenge is required, so the agent knows this is an authenticated, post-challenge read. However, nothing states when to pick this over read_merchant_transaction_evidence or read_transaction_record_evidence, and there is no guidance on obtaining the challenge.

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