Skip to main content
Glama

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; compare supported rails such as ACH, SEPA, EFT, FPS, IMPS, or SWIFT.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceRef": "<workspaceRef>",
      "portfolioRef": "<portfolioRef>",
      "network": "<network>",
      "receivingAmount": "<receivingAmount>"
    },
    "name": "simulate_fiat_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYesFiat payout rail / bank method
portfolioRefYesPortfolio exact name or slug
workspaceRefYesWorkspace exact name or slug
senderCurrencyNoStablecoin funding the payout (default USDC)
receivingAmountYesAmount the recipient should receive, as a decimal string in the receiving currency (e.g. "500000")
purposeOfPaymentNoPurpose-of-payment classification
receivingCurrencyNoISO 4217 receiving currency; defaults to the network default
recipientBankCountryNoISO 3166-1 alpha-2 recipient bank country; defaults to the network default

Output Schema

NameRequiredDescriptionDefault
noteNo
quoteNo
statusYes
corridorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered; the description adds the meaningful context that this is a pre-transfer simulation rather than an actual payout. It does not disclose quote validity/expiry or whether rates are indicative, which keeps it below a 5.

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 front-loaded sentence with the core action and returns stated first and the rail list second. No filler or redundant restatement of the title.

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 an output schema present, the description need not explain return values, and the annotations carry the safety profile, so the essentials are covered. The only meaningful gap is the absence of any note on quote lifetime or how rail defaults for currency/country are resolved.

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 every parameter is already documented, establishing the baseline of 3. The description only loosely echoes 'network' via the rail list and 'receivingAmount' via 'amount received'; it adds nothing on senderCurrency vs receivingCurrency, currency/country defaults, or purposeOfPayment.

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 (estimate) and resource (fiat payout quote) and enumerates what is returned: exchange rates, processing fees, amount received, and corridor limits. It also scopes the rail coverage (ACH, SEPA, EFT, FPS, IMPS, SWIFT), so an agent can tell this apart from any sibling tool without opening the schema.

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 phrase 'before sending money' gives a clear call condition, and 'compare supported rails' signals the intended comparison use case. It stops short of naming a follow-up execution tool or stating exclusions such as when a live quote is required instead, so it lands at 4 rather than 5.

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