Skip to main content
Glama

read_merchant_transaction_evidence

Read-only

Selected merchant reads its own Work Ticket evidence using merchant:work. Private proofs must stay private. The bundle hash is not exporter authentication, settlement confirmation or a quality assessment.

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": {
      "ticketId": "<ticketId>"
    },
    "name": "read_merchant_transaction_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real context beyond that: the required authorization scope (merchant:work), a privacy constraint ('Private proofs must stay private'), and explicit negative framing about what the bundle hash does not prove. It does not say what happens on an unknown ticketId or what the evidence payload contains, which keeps it out of the top band.

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

Conciseness3/5

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

Three short sentences with the scope and the authorization mechanism front-loaded, so there is little padding. The trade-off is that the terseness produces unexplained jargon ('Work Ticket evidence', 'bundle hash') rather than efficient clarity.

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?

There is no output schema, so the description should ideally say what a caller receives, and it does not. Still, for a single-parameter read with an annotation carrying the safety profile, the disclaimers about the bundle hash and the merchant:work scope cover the most likely misreadings, leaving only the return-value and parameter-origin gaps.

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% and there is one required parameter, yet the description never mentions ticketId — its meaning, where to obtain it, or whether it must belong to the calling merchant. The description adds no semantic value over the raw schema.

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

Purpose3/5

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

The description gives a verb ('reads') and a resource ('Work Ticket evidence') scoped to a selected merchant, which is more than a restatement of the name. However, 'evidence' is never defined, and the phrasing is dense enough that an agent cannot easily distinguish this from siblings such as read_transaction_evidence or read_transaction_record_evidence without opening their schemas.

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

Usage Guidelines2/5

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

It states who may call it ('selected merchant ... using merchant:work') but gives no when-to-use versus when-not guidance and never names an alternative among the many similarly named evidence/read tools. The agent must infer selection criteria from the tool name 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