Skip to main content
Glama
debridge-finance

deBridge

Official
by debridge-finance
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create_tx

Construct a cross-chain swap transaction via deBridge DLN protocol by specifying source and destination chains, token addresses, amounts, recipient, order authority addresses, affiliate fees, and operating expenses.

Instructions

Create a cross-chain swap transaction via the deBridge DLN protocol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
srcChainIdYesSource chain ID
srcChainTokenInYesToken address on source chain
srcChainTokenInAmountYesAmount in smallest units (wei, lamports)
dstChainIdYesDestination chain ID
dstChainTokenOutYesToken address on destination chain
dstChainTokenOutRecipientYesWallet address on destination chain to receive tokens
srcChainOrderAuthorityAddressYesAddress on source chain authorized to manage the order
dstChainOrderAuthorityAddressYesAddress on destination chain authorized to manage the order
dstChainTokenOutAmountNoOutput amount or 'auto' for best quote
affiliateFeePercentNoAffiliate fee percentage
affiliateFeeRecipientNoWallet address to receive affiliate fees
prependOperatingExpensesNoWhether to prepend estimated operating expenses to the input amount

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv0.1.0
    • changedInput schema / properties / affiliateFeePercent / description
      Previous value: -"Affiliate fee percentage (e.g. 0.1 for 0.1%)"New value: +"Affiliate fee percentage"
    • changedInput schema / properties / dstChainId / description
      Previous value: -"Destination chain ID. Examples: '1' (Ethereum), '56' (BNB Chain), '42161' (Arbitrum)"New value: +"Destination chain ID"
    • changedInput schema / properties / dstChainOrderAuthorityAddress / description
      Previous value: -"Address on the destination chain authorized to manage the order. Typically the recipient's wallet address"New value: +"Address on destination chain authorized to manage the order"
    • changedInput schema / properties / dstChainTokenOut / description
      Previous value: -"Token address on the destination chain to receive"New value: +"Token address on destination chain"
    • removedInput schema / properties / dstChainTokenOutAmount / default
      Removed value: -"auto"
    • changedInput schema / properties / dstChainTokenOutAmount / description
      Previous value: -"Output amount in smallest units, or 'auto' for best available quote (default: 'auto')"New value: +"Output amount or 'auto' for best quote"
    • changedInput schema / properties / dstChainTokenOutRecipient / description
      Previous value: -"Wallet address on the destination chain that will receive the tokens"New value: +"Wallet address on destination chain to receive tokens"
    • changedInput schema / properties / srcChainId / description
      Previous value: -"Source chain ID. Examples: '1' (Ethereum), '56' (BNB Chain), '137' (Polygon), '7565164' (Solana)"New value: +"Source chain ID"
    • changedInput schema / properties / srcChainOrderAuthorityAddress / description
      Previous value: -"Address on the source chain authorized to manage the order (cancel, etc). Typically the sender's wallet address"New value: +"Address on source chain authorized to manage the order"
    • changedInput schema / properties / srcChainTokenIn / description
      Previous value: -"Token address on the source chain to swap from. Use 0x0000000000000000000000000000000000000000 for native tokens (ETH, BNB, etc.)"New value: +"Token address on source chain"
    • changedInput schema / properties / srcChainTokenInAmount / description
      Previous value: -"Amount of source token in smallest units (wei, lamports). Example: '1000000000000000000' for 1 ETH (18 decimals), '1000000' for 1 USDC (6 decimals)"New value: +"Amount in smallest units (wei, lamports)"
  2. First observedv0.1.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided; description only says 'Create' without detailing side effects, permissions, or costs. Minimal behavioral context.

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?

Single sentence, front-loaded with purpose. Efficient but omits important context for conciseness.

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

Completeness2/5

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

No output schema or annotations; does not explain return values, errors, or behavior for a complex 12-parameter tool.

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% with descriptions; the tool description adds no extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it creates a cross-chain swap transaction via deBridge DLN protocol, distinguishing it from same-chain sibling tool.

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

Usage Guidelines3/5

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

The description implies usage for cross-chain swaps, contrasting with a same-chain sibling, but lacks explicit when-to-use or when-not-to-use guidance.

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/debridge-finance/debridge-mcp'

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