Skip to main content
Glama

Verify a signed check receipt

verify_receipt
Read-onlyIdempotent

Checks whether a receipt from this service is genuine and unchanged, using MDB Group's published public keys (https://b2b.mdb-group.info/.well-known/mdb-receipt-keys.json). Pass the receipt object (or the whole tool result that contains it, or its JSON text). Optionally pass the result it belongs to, to confirm that the result was not changed either. Answers "valid" (genuine and unchanged) or "invalid" with a reason: UNKNOWN_KEY_ID, BAD_SIGNATURE, MALFORMED, RESULT_MISMATCH or MALFORMED_RESULT (the given result could not be read). "unavailable" (KEYS_NOT_CONFIGURED) means this server has no usable key right now and could not judge the receipt; that is not "invalid". A genuine receipt proves that this service delivered the result at that time, not that the official source said so (except the VIES consultation number).

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": {
      "receipt": "<receipt>"
    },
    "name": "verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultNoOptional: the tool result the receipt was issued for, to check it against the receipt's result_sha256.
receiptYesThe receipt object, the whole result that carries a 'receipt' field, or the same as JSON text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the full outcome space — valid, invalid with one of five named reasons, and unavailable/KEYS_NOT_CONFIGURED — and crucially warns that 'unavailable' is not 'invalid', a distinction an agent would otherwise get wrong. It also states the evidentiary limit of a genuine receipt (proof of delivery at a time, not of official-source agreement), which is real semantic context not available from annotations.

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?

It is front-loaded with the core action and key source before the input instructions and outcome codes, and every clause carries information. The middle section is dense and crammed into long sentences with parenthetical error codes, which costs some readability.

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?

With no output schema, the description carries the return-value burden and does so fully: it enumerates the three top-level answers, all five invalid reasons, and the unavailable case. For a two-parameter, annotated, read-only verification tool this leaves nothing an agent needs unanswered.

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

Parameters4/5

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

Schema coverage is 100% and the schema already describes both parameters, so the baseline would be 3; however the description adds consequences the schema omits — that the optional result is checked against result_sha256 and that a failure surfaces as RESULT_MISMATCH or MALFORMED_RESULT. That makes the second parameter's effect concrete rather than merely descriptive.

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 opens with a precise verb and resource ('Checks whether a receipt ... is genuine and unchanged') and names the trust anchor (MDB Group's published public keys at a specific well-known URL). None of the sibling tools (check_vat_id, check_eori, vies_status, etc.) cover receipt verification, so an agent can route to it without ambiguity.

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?

It states concretely what to pass ('the receipt object, or the whole tool result that contains it, or its JSON text') and gives the conditional reason for the optional second argument ('to confirm that the result was not changed either'). What is missing is an explicit statement of when verification is warranted versus unnecessary (e.g., only for receipts issued by this service), but the usage context is otherwise clear.

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