Skip to main content
Glama

debridge-mcp

by io.github.debridge-finance

create_tx

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

Input Schema

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

Schema Changelog

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

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, and the description only says 'create', which implies mutation. It omits critical behavioral details like side effects (e.g., gas fees, wallet approval) for a blockchain transaction, leaving the agent with little insight.

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?

Single sentence with no filler, efficiently communicates the tool's primary purpose, and is front-loaded.

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?

Given the complexity of a 12-parameter cross-chain swap transaction, the description is too brief; it lacks information about return values, error handling, or workflow steps, making it incomplete for effective use.

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%, so parameters are well-documented in the schema. The description does not add extra meaning beyond 'create', but since the schema already covers parameter semantics, a baseline of 3 is appropriate.

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 clearly states the tool creates a cross-chain swap transaction via the deBridge DLN protocol, with a specific verb and resource, and distinguishes it from siblings like transaction_same_chain_swap.

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 on when to use this tool vs alternatives, no prerequisites or context provided; the description does not help differentiate usage scenarios.

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

All debridge-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: creating cross-chain transactions, retrieving instructions, listing supported chains, searching tokens, and creating same-chain swaps. No overlap.

Naming Consistency3/5

Most tools follow a verb_noun pattern (create_tx, get_instructions, get_supported_chains, search_tokens), but transaction_same_chain_swap is a noun phrase without a leading verb, breaking consistency.

Tool Count4/5

5 tools is a reasonable size for a cross-chain bridge server, covering essential functions without being too sparse or bloated.

Completeness3/5

The set covers core actions (create swap, list chains, search tokens) but lacks quote estimation or transaction status checking, which are common for such servers.

Resources