Skip to main content
Glama

MoneyTools payment-safety suite

Verify an approval proof

approval_verify
Read-only

Verify a Relay receipt_jws (free). The legacy 'proof' argument is also accepted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "approval_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
proofNo
receipt_jwsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, and the description is consistent with it (no contradiction). It adds useful context the annotations do not carry — that verification is free and that a deprecated 'proof' input is still honoured — but says nothing about what happens on an invalid receipt, whether an exception is raised, or whether cost is only avoided on success.

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 no filler; the primary input is named first and the legacy fallback follows. Slightly cryptic phrasing ('free', 'Relay') costs a little clarity but nothing is wasted.

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?

For a verification tool with no output schema and no parameter descriptions, the description should convey what a successful and failed verification return and which input is authoritative. It leaves both open, so an agent cannot predict the result shape or handle the dual-input case confidently.

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

Parameters3/5

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

With schema description coverage at 0%, the description is the only source of parameter meaning, and it does clarify that 'receipt_jws' is the primary input while 'proof' is a legacy alias still accepted. However, it never states precedence when both are supplied, nor the expected JWS format, and with zero required parameters the agent is left unsure whether supplying nothing is valid.

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 ('Verify') and a specific resource ('Relay receipt_jws'), which is concrete enough for an agent to recognise the operation, and it flags that 'proof' is a legacy alias. It does not explain what a Relay receipt is or what 'verified' means (boolean, decoded payload, error), so it stops short of distinguishing itself from the many sibling verify tools.

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 guidance on when to use this tool versus siblings such as payment_receipt_verify, signature_verify, or hmac_verify, and no prerequisites or exclusions. The only usable cue is the parenthetical '(free)', which hints at cost but not at selection.

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