Skip to main content
Glama
lnflash
by lnflash

bridge_create_transfer

Create fiat-to-crypto, crypto-to-fiat, or crypto-to-crypto transfers using supported payment rails. Use dry_run to validate before executing.

Instructions

Create a transfer to move money (fiat-to-crypto, crypto-to-fiat, or crypto-to-crypto)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoAmount to transfer (omit if flexible_amount is true)
dry_runNoIf true, validate without executing
currencyNoTransfer currency
on_behalf_ofYesCustomer ID on whose behalf the transfer is made
developer_feeNoFixed developer fee amount
source_addressNoSource crypto address (if applicable)
idempotency_keyNoOptional idempotency key for safe retries. Generated automatically when omitted.
source_currencyYesSource currency
destination_addressNoDestination crypto address (if applicable)
source_payment_railYesSource payment rail
destination_currencyYesDestination currency
developer_fee_percentNoDeveloper fee percentage
source_bridge_wallet_idNoSource Bridge wallet ID (if applicable)
destination_payment_railYesDestination payment rail
source_external_account_idNoSource external account ID (if applicable)
destination_bridge_wallet_idNoDestination Bridge wallet ID (if applicable)
destination_external_account_idNoDestination external account ID (if applicable)
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'create a transfer' without mentioning fees, idempotency, dry_run validation, or that funds may actually move. For a financial mutation tool, this is a critical gap.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the core purpose, though it could be too brief for the tool's complexity, slightly reducing structure effectiveness.

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

Completeness1/5

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

With 17 parameters, no output schema, and no annotations, the description is severely underspecified. It lacks combination rules, payment rail constraints, address requirements, fee behavior, and dry_run semantics, making it incomplete for safe invocation.

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?

The input schema provides full descriptions for all 17 parameters (100% coverage), so the description adds no additional parameter context. The schema already covers the semantics, so a baseline score of 3 applies.

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?

Description clearly states the action (Create), resource (transfer), and scope (fiat-to-crypto, crypto-to-fiat, or crypto-to-crypto). This distinguishes it from sibling create tools like bridge_create_wallet or bridge_create_external_account, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. It only states the basic purpose without context for scenarios like payment rail selection or on_behalf_of ownership.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lnflash/bridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server