MoneyTools Settle

Claim payment authorization

settle_gate_claim

Idempotent

Idempotency gate: claim an EIP-3009 authorization (payer+nonce) before settling. claimed:false means duplicate — do not settle again. 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": "settle_gate_claim"
  }
}

Input Schema

Name	Required	Description
`asset`	No	Token contract, default Base USDC.
`nonce`	No	EIP-3009 authorization nonce, 0x + 64 hex.
`payer`	No	Payer / agent wallet address 0x… (40 hex).
`apiKey`	No	Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
`network`	No	CAIP-2 network, default eip155:8453 (Base).
`paymentPayload`	No	The x402 PAYMENT-SIGNATURE / X-PAYMENT payload (base64 JSON or object).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds how idempotency surfaces to the caller (a 'claimed:false' return meaning duplicate), plus the auth requirement (mts_ key via header or apiKey) and plan limits. It doesn't say how long a claim is held or what a successful claim reserves, which would complete the picture.

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?

Front-loads the core concept ('Idempotency gate') and each sentence carries actionable content: duplicate handling, auth, trial fallback, plan cost. The telegraphic style and pricing/plan sentence are slightly dense but not wasteful.

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?

With no output schema, the description covers the one return field that matters operationally ('claimed:false') and fully covers authentication and fallback paths. Only the claim's lifecycle (lock duration, what claimed:true guarantees) is missing, which is a minor gap for a gate tool.

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?

Schema coverage is 100%, so all six parameters are already documented in the schema. The description only names payer+nonce as the identity tuple, which is a small framing addition rather than new per-parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('claim an EIP-3009 authorization (payer+nonce)') and immediately frames the tool's role as an idempotency gate ahead of settlement. That role distinguishes it from settle_gate_complete and settle_verify without needing their definitions.

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?

Gives a clear ordering rule ('claim ... before settling'), an explicit when-not ('claimed:false means duplicate — do not settle again'), and a named alternative for the no-key case (settle_trial_key with its free tier). It doesn't compare against settle_verify or settle_gate_complete, which is the only gap.

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?