Skip to main content
Glama

bridge_transfer

Move tokens between blockchains with Stargate protocol: automatically fetches quote, processes approvals, and broadcasts transactions to the source chain.

Instructions

Execute a cross-chain token bridge transfer using the Stargate protocol.

This tool fetches a quote internally (using provided chains and default addresses), constructs and signs transactions using the private key from the .env file, broadcasts them sequentially to the source chain, and waits for confirmations. It handles approvals and bridge steps. Source address is derived from PRIVATE_KEY. Destination address defaults to source if not provided.

Parameters:
- src_chain_key (str): Source chain key (e.g., 'ethereum').
- dst_chain_key (str): Destination chain key (e.g., 'polygon').
- src_token (str): Source token contract address.
- dst_token (str): Destination token contract address.
- src_amount (float): Human-readable amount to bridge (e.g., 1.0).
- dst_amount_min (float): Minimum expected destination amount for slippage (e.g., 0.99).
- dst_address (Optional[str]): Destination wallet address. If omitted, uses source address from PRIVATE_KEY.

Returns:
- str: Markdown-formatted string with success message including transaction hashes for each step, or an error message if any step fails (e.g., invalid key, no quote, RPC failure, or transaction revert).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dst_tokenYes
src_tokenYes
src_amountYes
dst_addressNo
dst_chain_keyYes
src_chain_keyYes
dst_amount_minYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses the internal flow: fetches a quote, signs transactions using the private key from .env, broadcasts sequentially, waits for confirmations, handles approvals, derives the source address from PRIVATE_KEY, and defaults destination address to source. It also lists error cases and return format.

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 well-structured: purpose sentence, process paragraph, parameter list, and return explanation. It is verbose but every sentence adds value. Some redundancy exists with the schema parameter list, but the extra semantics justify the length.

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?

Given the tool's complexity (multi-step bridge transfer) and absence of annotations, the description is remarkably complete. It covers the execution flow, key derivation, approvals, sequential broadcasting, confirmation waits, return format, and potential error conditions, leaving few open questions for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by providing meaningful context for each parameter, including examples (e.g., 'ethereum', 'polygon'), clarifying that src_amount is human-readable, dst_amount_min is for slippage, and dst_address defaults to the source address if omitted.

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+resource: 'Execute a cross-chain token bridge transfer using the Stargate protocol.' This clearly distinguishes it from sibling tools (list_chains, list_bridgeable_tokens, get_quotes) which are informational and not execution-oriented.

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?

The description clearly implies when to use this tool (to actually execute a bridge transfer) and states that it fetches a quote internally, signaling that a separate get_quotes call may not be necessary. However, it does not explicitly say when NOT to use this tool or compare it to alternatives.

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/kukapay/stargate-bridge-mcp'

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