Skip to main content
Glama

Chainflip Broker as a Service

by io.chainflip-broker

Start DCA Swap

start_dca_swap

Start a DCA (Dollar Cost Averaging) cross-chain swap that splits into multiple sub-swaps over time. Returns the deposit address. API key is optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNoOptional partner API key.
sourceAssetYesSource asset identifier (e.g., 'btc.btc', 'eth.eth', 'usdc.eth')
minimumPriceNoOptional minimum accepted price as a destination-per-source ratio (e.g., for a btc.btc to eth.eth swap, 28.5 means 1 BTC gets at least 28.5 ETH). When omitted, automatically calculated from current pool prices with 2% slippage tolerance. Set to 0 to accept any price.
refundAddressYesRefund address on the source chain, used if minimum price cannot be met
numberOfChunksYesNumber of sub-swaps for DCA (Dollar Cost Averaging). Must be >= 1.
destinationAssetYesDestination asset identifier (e.g., 'eth.eth', 'btc.btc', 'sol.sol')
destinationAddressYesDestination address on the target chain
chunkIntervalBlocksNoOptional delay between DCA sub-swaps in state-chain blocks (1 block = 6 seconds). Defaults to 2 blocks (12 seconds).

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-idempotent. Description adds 'Returns deposit address' but no further behavioral details like state changes or approval needs. No contradiction.

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?

Two sentences, front-loaded with purpose and key return value. Every sentence earns its place.

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

Completeness3/5

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

With 8 parameters and no output schema, description is brief. Does not explain DCA mechanism, pricing, or outcome after creation. Leaves gaps for complex usage.

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 baseline 3. Description adds some value (explains cross-chain, sub-swaps, deposit address) but does not elaborate on individual parameters beyond schema.

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 it starts a DCA cross-chain swap with sub-swaps, distinguishing it from sibling tools like start_swap (single swap). Verb 'start' and resource 'DCA swap' are specific.

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?

No explicit when-to-use or when-not-to-use guidance. Mentions API key optional but no context on choosing between DCA and regular swap. Implies usage for splitting swaps over time.

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

All Chainflip Broker as a Service 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

A4/5.0
Disambiguation4/5

Most tools have distinct purposes: status checking, quotes, asset listing, swap initiation. The two quote tools (get_native_quotes and get_quotes) differ in input units, which is clarified in descriptions but could still cause minor confusion for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (check_status, get_native_quotes, get_quotes, list_assets, start_dca_swap, start_swap).

Tool Count5/5

With 6 tools covering quotes, asset info, swap initiation, and status checks, the count is well-scoped for a swap service without being excessive or insufficient.

Completeness4/5

The tool set covers the core swap lifecycle: get quotes, list assets, start swaps (including DCA), and check status. Missing potential operations like cancel or list past swaps, but these are not essential for the primary use case.

Resources