Skip to main content
Glama
Sign In

Chainflip Broker as a Service

by io.chainflip-broker
OverviewDiscussionsAdmin

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

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).
livePriceSlippageTolerancePercentNoOptional live price protection: how far, in percent (0 to 100, at most 2 decimals, e.g. 0.5), the execution price may fall below Chainflip's oracle price before a sub-swap is retried and the rest refunded. Use a quote's recommendedLivePriceSlippageTolerancePercent. Rejected when either asset has no oracle price on Chainflip. When omitted, Chainflip's default protection for the pair applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / livePriceSlippageTolerancePercent
      Added value: +{
+  "default": null,
+  "description": "Optional live price protection: how far, in percent (0 to 100, at most 2 decimals, e.g. 0.5), the execution price may fall below Chainflip's oracle price before a sub-swap is retried and the rest refunded. Use a quote's recommendedLivePriceSlippageTolerancePercent. Rejected when either asset has no oracle price on Chainflip. When omitted, Chainflip's default protection for the pair applies.",
+  "type": [
+    "number",
+    "null"
+  ]
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), open-world, non-idempotent, non-destructive semantics, so the safety profile is covered. The description usefully adds that it 'Returns the deposit address,' signaling a deposit-required flow, but omits the critical follow-up (funding that address and later checking via check_status) and any failure/refund behavior.

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?

Three short sentences, front-loaded with the core purpose and the non-obvious return behavior. Minor redundancy: 'API key is optional' restates the schema's nullable default for apiKey, but it is not costly.

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 no output schema, the description correctly compensates by stating it returns a deposit address. However, for a non-idempotent, open-world swap tool it leaves the operational lifecycle unexplained (that funds must be sent to that address, and that check_status tracks progress), which is the main gap for correct 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?

Schema description coverage is 100% (9/9 params documented, including nuanced fields like minimumPrice and livePriceSlippageTolerancePercent), so the schema carries full parameter meaning. The description adds nothing beyond what the schema already states, which is the expected baseline when coverage is complete.

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?

States a specific verb+resource ('Start a DCA cross-chain swap') and adds the defining trait that separates it from the sibling start_swap: it 'splits into multiple sub-swaps over time.' That distinction lets an agent route correctly without opening start_swap's schema, though it never names start_swap explicitly.

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 when-to-use guidance and no comparison to the single-swap sibling start_swap. The only contextual hint is 'API key is optional,' which does not tell an agent when DCA is preferable to a one-shot swap or what prerequisites exist.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources