Skip to main content
Glama
Stables MCP Server

Stables MCP Server

Official

Create transfer (moves money)

create_transfer
Destructive

Create a transfer from an active quote, returning deposit instructions for fund_transfer or debiting your organisation's balance to start a payout immediately with prefund_balance.

Instructions

Create a transfer from an active quote. The quote must not be expired. With fundingSource fund_transfer (the default) this only creates the transfer and returns deposit instructions; no money moves until someone deposits the funds. With prefund_balance it debits your organisation's balance and starts the payout immediately, so this moves real money: 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. To pay one of the organisation's saved beneficiaries, set destinationType to beneficiary and pass its beneficiaryId instead of bank details.

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": {
      "customerId": "<customerId>",
      "quoteId": "<quoteId>"
    },
    "name": "create_transfer"
  }
}

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
beneficiaryIdNoSaved beneficiary id when destinationType is beneficiary. It supplies the recipient and bank details, so the bank fields are ignored; archived beneficiaries are refused
fundingSourceNofund_transfer (default) creates the transfer and returns deposit instructions; nothing moves until a person deposits the funds. prefund_balance debits your organisation's balance and starts the payout immediately, so it needs explicit human approval. 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), a wallet address, or a saved beneficiarybank
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. Changed6 schema fields changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / beneficiaryId
      Added value: +{
      +  "description": "Saved beneficiary id when destinationType is beneficiary. It supplies the recipient and bank details, so the bank fields are ignored; archived beneficiaries are refused",
      +  "type": "string"
      +}
    • changedInput schema / properties / destinationType / description
      Previous value: -"Payout target: a bank account (off-ramp) or a wallet address"New value: +"Payout target: a bank account (off-ramp), a wallet address, or a saved beneficiary"
    • changedInput schema / properties / destinationType / enum
      Previous value: -[
      -  "bank",
      -  "crypto"
      -]New value: +[
      +  "bank",
      +  "crypto",
      +  "beneficiary"
      +]
    • changedInput schema / properties / fundingSource / description
      Previous value: -"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"New value: +"fund_transfer (default) creates the transfer and returns deposit instructions; nothing moves until a person deposits the funds. prefund_balance debits your organisation's balance and starts the payout immediately, so it needs explicit human approval. Check get_balance first: transfers_enabled must be true and the quote's source asset must be held on its network"
    • addedInput schema / properties / metadata / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. 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"
  3. First observedv1.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructive=true and non-idempotent, and the description adds the critical operational context: the default path does not move money until a person deposits funds, while prefund_balance debits the organisation's balance immediately. It also warns that expired quotes are rejected and that human approval is required for prefunded payouts.

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?

The description is five tight sentences that front-load the action and the money-movement warning before describing corridor and beneficiary variants. Every sentence carries operational weight, with no repetition of schema-only field definitions.

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?

For a 35-parameter destructive tool with no output schema, the description covers the essential decision points: funding source behaviour, human approval, quote validity, corridor-specific recipient requirements, and the saved-beneficiary shortcut. The remaining field-level details are fully documented in the schema.

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. The description still adds value by synthesising cross-field conditional logic: recipientType, full beneficiary address, and dateOfBirth for AED/CAD/EUR/GBP/MXN/USD payouts, and destinationType=beneficiary with beneficiaryId replacing bank details.

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 opens with a specific verb and resource: 'Create a transfer from an active quote.' It immediately distinguishes the tool from quote creation and explains the two funding paths, so an agent can identify the 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when/when-not guidance: use fund_transfer for deposit instructions with no money movement, use prefund_balance only after explicit human approval because real money moves immediately. It also names corridor-specific prerequisites and the saved-beneficiary alternative to raw bank details.

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