Skip to main content
Glama
stables-money

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_virtual_account

Create a payment route for a customer to collect fiat deposits, convert them to stablecoin, and pay out to a specified wallet; payout address is mandatory.

Instructions

Create a payment route (virtual bank account) so a customer can receive fiat deposits that convert to a stablecoin and pay out to a wallet. The payout destination is mandatory: the API refuses a fiat-to-crypto route without one. Deposit handling is set server-side and defaults to auto_payout; change it afterwards with update_virtual_account.

Input Schema

NameRequiredDescriptionDefault
customerIdYesThe customer ID to create the payment route for
sourceCurrencyYesFiat currency the route collects in (e.g. 'AUD', 'USD', 'EUR')
destinationAddressYesWallet address deposits are paid out to. Validated against the chosen network
destinationCurrencyNoStablecoin to receiveusdt
destinationPaymentRailYesBlockchain network the payout address belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.4.0
    • changedInput schema / properties / customerId / description
      Previous value: -"The customer ID to create the virtual account for"New value: +"The customer ID to create the payment route for"
    • removedInput schema / properties / depositHandlingMode
      Removed value: -{
-  "description": "How to handle deposits: 'auto_payout' converts and sends to wallet, 'hold' keeps as fiat, 'manual' requires approval",
-  "enum": [
-    "auto_payout",
-    "hold",
-    "manual"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / destinationAddress / description
      Previous value: -"Crypto wallet address for payouts"New value: +"Wallet address deposits are paid out to. Validated against the chosen network"
    • addedInput schema / properties / destinationCurrency / default
      Added value: +"usdt"
    • changedInput schema / properties / destinationCurrency / description
      Previous value: -"Stablecoin to receive (default: usdc)"New value: +"Stablecoin to receive"
    • changedInput schema / properties / destinationPaymentRail / description
      Previous value: -"Blockchain network for the destination wallet"New value: +"Blockchain network the payout address belongs to"
    • changedInput schema / properties / sourceCurrency / description
      Previous value: -"Currency for the virtual account (e.g., 'USD', 'EUR', 'GBP')"New value: +"Fiat currency the route collects in (e.g. 'AUD', 'USD', 'EUR')"
    • changedInput schema / required
      Previous value: -[
-  "customerId",
-  "sourceCurrency"
-]New value: +[
+  "customerId",
+  "sourceCurrency",
+  "destinationAddress",
+  "destinationPaymentRail"
+]
  2. First observedv1.4.0

TDQS

A4.2/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 disclose meaningful behavior: a server-side validation that rejects routes lacking a destination, a server-side default of auto_payout, and the fact that deposit handling is mutable after creation. It omits auth/permission requirements and idempotency behavior, keeping it short of 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?

Three sentences, no filler, and the core purpose plus the critical constraint (mandatory destination) are front-loaded before the optional follow-up guidance.

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 mutation tool with no annotations and no output schema, the description covers purpose, the blocking validation, defaults, and the follow-up tool. It leaves the response shape (e.g., returned route/account identifiers) unspecified, which is a minor gap given no output schema exists.

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%, so the schema already documents all five parameters including enums and the destinationCurrency default. The description adds the mandatory nature of the payout destination and the network-validation of destinationAddress, but nothing beyond what the schema states.

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+resource ("Create a payment route (virtual bank account)") and explains the end-to-end effect: receive fiat deposits, convert to stablecoin, pay out to a wallet. It is clearly distinguishable from siblings like update_virtual_account and create_customer.

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?

It states a hard precondition (payout destination is mandatory; the API refuses a fiat-to-crypto route without one) and routes the agent to update_virtual_account for later changes to deposit handling. It does not cover when to prefer other route types or account-creation alternatives, but the primary when-to-use context is explicit.

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

Deploy Server

Other Tools