Skip to main content
Glama

Verify a Payment Guard receipt (free)

verify_receipt
Read-only

Free. Verify that a receipt (payload_json + signature) was issued by Agent Payment Guard and has not been altered.

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

Input Schema

NameRequiredDescriptionDefault
signatureYes
payload_jsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 useful context — that it is free and that it validates both issuer authenticity and payload integrity — but says nothing about outcomes on an invalid receipt (false vs. error), or any rate limits.

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?

Two short sentences with the cost signal front-loaded and the validation semantics immediately after. No wasted wording, though the fragment 'Free.' is stylistically abrupt.

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

Completeness3/5

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

For a small two-parameter read-only tool this is mostly adequate, but with no output schema the description leaves the return contract (boolean, structured result, or exception on failure) entirely implicit — the one thing a verification tool most needs to state.

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, yet it only repeats the parameter names from the schema. It never explains what payload_json contains (the receipt body as JSON text?) or what encoding the signature uses, which matters for calling the tool correctly.

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 names a specific verb (verify) and resource (receipt), and states the two guarantees being checked: issuance by Agent Payment Guard and absence of alteration. That is enough to tell it apart from siblings like check_token or check_payment_counterparty, which operate on different resources, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. 'Free.' is a pricing signal rather than usage guidance; the agent must infer that this is a pre-trust check on a receipt.

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