MoneyTools Settle

Update delivery receipt

receipt_update

Move a receipt paid -> delivered | failed | refunded (refundTx optional). Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

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": "receipt_update"
  }
}

Input Schema

Name	Required	Description
`ref`	No	Your order / request id (idempotency key).
`note`	No	Free-text note (max 200 chars).
`apiKey`	No	Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
`status`	No	New status (see tool description).
`refundTx`	No	Refund tx hash on Base, 0x + 64 hex.
`receiptId`	No	Receipt id str_… (or use ref).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive mutation, so the bar is lower. The description goes beyond them with auth mechanics (X-API-Key header or apiKey argument), trial limits (50 calls/7 days) and plan pricing, which an agent needs before calling. It does not disclose idempotency semantics even though the schema labels `ref` an idempotency key.

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 state transition, then auth, then the fallback path, all in three compact clauses. The pricing/plan sentence is slightly promotional but still carries actionable information for a caller lacking a key.

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 6-parameter mutation with no output schema, it covers the operation, allowed transitions, auth path and fallback tool. It leaves gaps on idempotency behavior of `ref`, error outcomes for invalid transitions, and which of `receiptId`/`ref` is preferred.

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%, so the baseline is 3. The description adds real meaning by defining the permitted `status` values and noting that `refundTx` is optional (only relevant for the refunded transition), which the schema's bare 'see tool description' back-reference depends on.

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 names a specific verb and resource ('Move a receipt') and enumerates the exact state machine: paid -> delivered | failed | refunded. This clearly separates it from receipt_create (creating) and receipt_get (reading).

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 the precondition for use (a mts_ key) and routes the caller without a key to settle_trial_key, which is explicit alternative-tool guidance. It does not, however, say anything about when the update should be rejected or what happens if the receipt is not currently 'paid'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MoneyTools Settle tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?