MoneyTools Settle

Complete gate (settled/failed)

settle_gate_complete

Idempotent

Mark a claimed authorization settled or failed (failed allows a retry). 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_complete"
  }
}

Input Schema

Name	Required	Description
`tx`	No	Settlement tx hash on Base, 0x + 64 hex.
`apiKey`	No	Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
`gateId`	No	Gate id from settle_gate_claim.
`status`	No	New status (see tool description).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, so the description is free to add the things annotations cannot: the mts_ key requirement, header-vs-argument auth options, the fact that a 'failed' outcome permits a retry, and the paid plan's call allowance. It does not say what happens to an already-settled gate or what the response confirms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by auth, then the no-key escape hatch, then pricing. Every sentence carries distinct information and none repeats the schema or annotations.

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 mutating, auth-gated tool with no output schema, the description covers credentials, fallback path, cost, and retry behavior adequately. The remaining gap is that no parameters are marked required, and the description does not clarify which of tx/gateId/status must be supplied for a valid call.

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, but the description adds real meaning by enumerating the accepted status values (settled/failed) and explaining the retry consequence of 'failed'. The tx and gateId parameters are left to the schema's own text.

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 ('Mark a claimed authorization settled or failed') and ties it to the preceding claim step, which cleanly separates it from settle_gate_claim. The parenthetical on failure semantics adds precision beyond the name.

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?

Establishes the usage context (after a gate has been claimed) and explicitly routes agents without credentials to settle_trial_key, including that it is free with a 50 calls/7 days allowance. It does not state when this tool should NOT be used (e.g. before a claim exists), so it stops short of full when/when-not guidance.

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?