Tokenbooks - crypto and fiat accounting and payments

Simulate Fiat Payout Quote

simulate_fiat_quote

Read-onlyIdempotent

Estimate exchange rates, processing fees, amount received, and corridor limits for a bank payout before sending money; use it to compare supported rails such as ACH, SEPA, EFT, FPS, IMPS, or SWIFT.

Input Schema

TableJSON Schema

Name	Required	Description
`network`	Yes	Fiat payout rail / bank method
`portfolioRef`	Yes	Portfolio exact name or slug
`workspaceRef`	Yes	Workspace exact name or slug
`senderCurrency`	No	Stablecoin funding the payout (default USDC)
`receivingAmount`	Yes	Amount the recipient should receive, as a decimal string in the receiving currency (e.g. "500000")
`purposeOfPayment`	No	Purpose-of-payment classification
`receivingCurrency`	No	ISO 4217 receiving currency; defaults to the network default
`recipientBankCountry`	No	ISO 3166-1 alpha-2 recipient bank country; defaults to the network default

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`quote`	No
`status`	Yes
`corridor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "corridor": {
+      "additionalProperties": false,
+      "properties": {
+        "amountBounds": {
+          "additionalProperties": false,
+          "properties": {
+            "maxAmount": {
+              "type": "string"
+            },
+            "minAmount": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "minAmount",
+            "maxAmount"
+          ],
+          "type": "object"
+        },
+        "network": {
+          "type": "string"
+        },
+        "receivingCurrency": {
+          "type": "string"
+        },
+        "recipientBankCountry": {
+          "type": "string"
+        },
+        "senderCurrency": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "network",
+        "receivingCurrency",
+        "recipientBankCountry",
+        "senderCurrency"
+      ],
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "quote": {
+      "additionalProperties": false,
+      "properties": {
+        "exchangeRate": {
+          "type": "string"
+        },
+        "itemizedFees": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "amount": {
+                "type": "string"
+              },
+              "key": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "percentage": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "key",
+              "label",
+              "amount"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "processingFee": {
+          "type": "string"
+        },
+        "quoteValiditySeconds": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "receivingCurrency": {
+          "type": "string"
+        },
+        "senderCurrency": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "totalReceivable": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "exchangeRate",
+        "senderCurrency",
+        "receivingCurrency",
+        "processingFee",
+        "itemizedFees",
+        "totalReceivable",
+        "quoteValiditySeconds",
+        "summary"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "quoted",
+        "corridor_unavailable",
+        "amount_out_of_range",
+        "limit_skipped"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "corridor"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the tool produces estimates, does not send money, and supports comparing multiple rails. This is consistent with the annotations.

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?

A single, well-structured sentence that front-loads what the tool does, lists concrete outputs, and gives rail examples. No wasted words and no repetition of schema content.

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

Completeness5/5

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

The description, combined with full parameter docs, rich enums, an output schema, and safety annotations, gives an agent everything needed to select and invoke the tool correctly. It clearly states the tool is for simulation/estimation before sending money, which is the core contextual requirement.

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 description coverage is 100%, and every parameter already has a meaningful description and enum where applicable. The tool description adds context about the outputs produced rather than new parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Estimate') and names the resource and outputs: exchange rates, processing fees, amount received, and corridor limits. It also distinguishes the tool from execution-oriented siblings by emphasizing 'before sending money' and by listing supported rails.

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?

The description explicitly frames the tool as a pre-send estimation/compare utility across rails such as ACH, SEPA, EFT, FPS, IMPS, or SWIFT. It does not explicitly name excluded alternatives or say 'use confirm_transaction to actually send,' but the use case is clear enough for an agent to route correctly.

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

All Tokenbooks - crypto and fiat accounting and payments 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?