Skip to main content
Glama
stables-money

Stables MCP Server

Official

create_transfer

Execute a transfer using an active, unexpired quote to move real money. Requires explicit human approval and beneficiary details for supported payout corridors.

Instructions

Execute a transfer using an active quote. The quote must not be expired. This initiates real money movement, so get explicit human approval first. For payouts in AED, CAD, EUR, GBP, MXN, USD you must also supply recipientType, the full beneficiary address, and dateOfBirth when the recipient is an individual.

Input Schema

NameRequiredDescriptionDefault
ibanNoIBAN (EU/international)
cnapsNoCNAPS (China)
payIdNoPayID alias (AUD only). Requires payIdType
bicCodeNoBIC (EUR/GBP international)
bsbCodeNoBSB code (Australia)
quoteIdYesThe quote ID to execute
bankCodeNoBank code / institution number (CAD)
bankNameNoName of the destination bank
ifscCodeNoIFSC code (India)
metadataNoOptional metadata
sortCodeNoSort code (UK)
payIdTypeNoPayID alias type. Required when payId is given
swiftCodeNoSWIFT code
branchCodeNoBranch code / transit number (CAD)
customerIdYesThe customer ID for this transfer
accountTypeNoAccount type. Required for CAD and USD bank payouts
addressCityNoBeneficiary city
bankCountryNoBank country, ISO 2-letter (e.g. 'AU', 'US')
dateOfBirthNoBeneficiary date of birth, YYYY-MM-DD. Required when recipientType is individual for AED, CAD, EUR, GBP, MXN, USD
purposeCodeNoPurpose of the transfer (e.g. 'SALARY'). Required on some corridors
addressStateNoBeneficiary state or region
bankCurrencyNoPayout currency, ISO 3-letter (e.g. 'EUR')
accountNumberNoBank account number, if not using IBAN
addressStreetNoBeneficiary street address
fundingSourceNofund_transfer (default) returns deposit instructions for the customer; prefund_balance pays from your organisation's balance and starts immediately. Check get_balance first: transfers_enabled must be true and the quote's source asset must be held on its network
recipientTypeNoBeneficiary type. Required for AED, CAD, EUR, GBP, MXN, USD
routingNumberNoABA routing number (US)
addressCountryNoBeneficiary country, ISO 2-letter. The complete address is required for AED, CAD, EUR, GBP, MXN, USD
destinationTypeNoPayout target: a bank account (off-ramp) or a wallet addressbank
accountHolderNameNoAccount holder's full name, or the company name when recipientType is business
addressPostalCodeNoBeneficiary postal code
destinationAddressNoWallet address when destinationType is crypto
destinationNetworkNoBlockchain network when destinationType is crypto (e.g. 'polygon')
destinationCurrencyNoStablecoin to deliver when destinationType is crypto (e.g. 'USDT')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changedv2.4.0
    • changedInput schema / properties / accountHolderName / description
      Previous value: -"Bank account holder's full name (required for off-ramp)"New value: +"Account holder's full name, or the company name when recipientType is business"
    • changedInput schema / properties / accountNumber / description
      Previous value: -"Bank account number (if not using IBAN)"New value: +"Bank account number, if not using IBAN"
    • changedInput schema / properties / accountType / description
      Previous value: -"Type of bank account"New value: +"Account type. Required for CAD and USD bank payouts"
    • addedInput schema / properties / addressCity
      Added value: +{
      +  "description": "Beneficiary city",
      +  "type": "string"
      +}
    • addedInput schema / properties / addressCountry
      Added value: +{
      +  "description": "Beneficiary country, ISO 2-letter. The complete address is required for AED, CAD, EUR, GBP, MXN, USD",
      +  "type": "string"
      +}
    • addedInput schema / properties / addressPostalCode
      Added value: +{
      +  "description": "Beneficiary postal code",
      +  "type": "string"
      +}
    • addedInput schema / properties / addressState
      Added value: +{
      +  "description": "Beneficiary state or region",
      +  "type": "string"
      +}
    • addedInput schema / properties / addressStreet
      Added value: +{
      +  "description": "Beneficiary street address",
      +  "type": "string"
      +}
    • addedInput schema / properties / bankCode
      Added value: +{
      +  "description": "Bank code / institution number (CAD)",
      +  "type": "string"
      +}
    • changedInput schema / properties / bankCountry / description
      Previous value: -"Two-letter country code of the bank (e.g., 'AU', 'US')"New value: +"Bank country, ISO 2-letter (e.g. 'AU', 'US')"
    • changedInput schema / properties / bankCurrency / description
      Previous value: -"Currency for the bank payout (e.g., 'EUR', 'USD', 'AUD')"New value: +"Payout currency, ISO 3-letter (e.g. 'EUR')"
    • changedInput schema / properties / bankName / description
      Previous value: -"Name of the destination bank (required for off-ramp)"New value: +"Name of the destination bank"
    • addedInput schema / properties / bicCode
      Added value: +{
      +  "description": "BIC (EUR/GBP international)",
      +  "type": "string"
      +}
    • addedInput schema / properties / branchCode
      Added value: +{
      +  "description": "Branch code / transit number (CAD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / cnaps
      Added value: +{
      +  "description": "CNAPS (China)",
      +  "type": "string"
      +}
    • addedInput schema / properties / dateOfBirth
      Added value: +{
      +  "description": "Beneficiary date of birth, YYYY-MM-DD. Required when recipientType is individual for AED, CAD, EUR, GBP, MXN, USD",
      +  "type": "string"
      +}
    • addedInput schema / properties / destinationAddress
      Added value: +{
      +  "description": "Wallet address when destinationType is crypto",
      +  "type": "string"
      +}
    • addedInput schema / properties / destinationCurrency
      Added value: +{
      +  "description": "Stablecoin to deliver when destinationType is crypto (e.g. 'USDT')",
      +  "type": "string"
      +}
    • addedInput schema / properties / destinationNetwork
      Added value: +{
      +  "description": "Blockchain network when destinationType is crypto (e.g. 'polygon')",
      +  "type": "string"
      +}
    • addedInput schema / properties / destinationType
      Added value: +{
      +  "default": "bank",
      +  "description": "Payout target: a bank account (off-ramp) or a wallet address",
      +  "enum": [
      +    "bank",
      +    "crypto"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / fundingSource
      Added value: +{
      +  "description": "fund_transfer (default) returns deposit instructions for the customer; prefund_balance pays from your organisation's balance and starts immediately. Check get_balance first: transfers_enabled must be true and the quote's source asset must be held on its network",
      +  "enum": [
      +    "fund_transfer",
      +    "prefund_balance"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / iban / description
      Previous value: -"IBAN for the destination bank account (EU/international)"New value: +"IBAN (EU/international)"
    • changedInput schema / properties / metadata / description
      Previous value: -"Optional metadata to attach to the transfer"New value: +"Optional metadata"
    • addedInput schema / properties / payId
      Added value: +{
      +  "description": "PayID alias (AUD only). Requires payIdType",
      +  "type": "string"
      +}
    • addedInput schema / properties / payIdType
      Added value: +{
      +  "description": "PayID alias type. Required when payId is given",
      +  "enum": [
      +    "email",
      +    "phone_number",
      +    "abn",
      +    "acn",
      +    "organisation_id"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / purposeCode
      Added value: +{
      +  "description": "Purpose of the transfer (e.g. 'SALARY'). Required on some corridors",
      +  "enum": [
      +    "PAYMENT_FOR_SERVICES",
      +    "PAYMENT_FOR_SOFTWARE",
      +    "PAYMENT_FOR_IMPORTED_GOODS",
      +    "TRAVEL_SERVICES",
      +    "VENDOR_CONTRACTOR_PAYOUTS",
      +    "TRANSFER_TO_OWN_ACCOUNT",
      +    "INVESTMENT_IN_SHARES",
      +    "PURCHASE_OF_PROPERTY",
      +    "REPAYMENT_OF_LOANS",
      +    "SALARY",
      +    "PAYMENT_OF_PROPERTY_RENTAL",
      +    "INFORMATION_SERVICE_CHARGES",
      +    "ADVERTISING_PR_EXPENSES",
      +    "ROYALTY_FEES",
      +    "BROKER_COMMITMENT_FEES",
      +    "ADVISOR_TECHNICAL_FEES",
      +    "REPRESENTATIVE_OFFICE_EXPENSES",
      +    "TAX_PAYMENT",
      +    "TRANSPORTATION_FEES_FOR_GOODS",
      +    "CONSTRUCTION_COSTS",
      +    "INSURANCE_PREMIUM",
      +    "GENERAL_GOODS_TRADES",
      +    "INSURANCE_CLAIMS_PAYMENT",
      +    "FAMILY_MAINTENANCE",
      +    "EDUCATION_EXPENSES",
      +    "MEDICAL_TREATMENT",
      +    "DONATIONS",
      +    "MUTUAL_FUND_INVESTMENT",
      +    "CURRENCY_EXCHANGE",
      +    "USER_WITHDRAWAL",
      +    "ADVANCE_PAYMENTS_FOR_GOODS",
      +    "VENDOR_CONTRACTOR_SOFTWARE_PAYOUTS",
      +    "MERCHANT_SETTLEMENT",
      +    "REPATRIATION_FUND_SETTLEMENT",
      +    "PERSONAL_REMITTANCE",
      +    "RETURN_OF_FUNDS"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / recipientType
      Added value: +{
      +  "description": "Beneficiary type. Required for AED, CAD, EUR, GBP, MXN, USD",
      +  "enum": [
      +    "individual",
      +    "business"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / swiftCode / description
      Previous value: -"SWIFT/BIC code for international transfers"New value: +"SWIFT code"
  2. First observedv1.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that this initiates real money movement, requires human approval, and depends on an unexpired quote. It does not cover failure/idempotency behavior or the fundingSource/destinationType branches, leaving some gaps.

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?

Four sentences, front-loaded with the core action and then the critical constraints. Every sentence earns its place, though the final corridor sentence is dense and could be slightly tightened.

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 34-parameter mutation tool with no annotations and no output schema, the description covers the essential safety and corridor requirements. It omits the crypto-destination and fundingSource paths, but those are thoroughly documented in the schema, so the gap is minor.

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 cross-field conditional logic (recipientType + full address + dateOfBirth required for AED/CAD/EUR/GBP/MXN/USD when the recipient is an individual) that is not obvious from individual field descriptions.

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 ('Execute a transfer using an active quote') and clearly distinguishes itself from siblings like create_quote (prerequisite) and get_transfer/list_transfers (read operations). An agent can identify the action 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?

Gives concrete preconditions: the quote must not be expired and explicit human approval is required before execution. It also states corridor-specific requirements. It stops short of naming explicit alternatives or when-not-to-use cases, but the context is clear.

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