Skip to main content
Glama

Chainflip Broker as a Service

by io.chainflip-broker

Get Native Quotes

get_native_quotes
Read-only

Get swap quotes for exchanging one crypto asset to another using native (smallest unit) amounts. Returns available quotes with exchange rates, fees, and estimated output amounts. Use this when you have amounts in native units (e.g., satoshis for BTC, wei for ETH). API key is optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount to swap in native units (e.g., '100000000' for 1 BTC in satoshis)
apiKeyNoOptional partner API key.
sourceAssetYesSource asset identifier (e.g., 'btc.btc', 'eth.eth', 'usdc.eth')
destinationAssetYesDestination asset identifier (e.g., 'eth.eth', 'btc.btc', 'sol.sol')

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds context about return fields (exchange rates, fees, estimated output) and API key optionality. No contradictions. Does not mention rate limits or permissions, but annotations cover safety adequately.

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?

Three sentences, no wasted words. Front-loaded with purpose and key distinguishing feature (native units). Each sentence contributes meaning.

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

Completeness4/5

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

For a read-only quote tool with complete schema descriptions and safety annotations, the description covers return values and optional API key. Could mention quote multiplicity or that it's non-executing, but overall sufficient for typical 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% with detailed parameter descriptions. The description reinforces the native unit concept with examples, adding marginal value beyond the schema. Baseline 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?

Clearly states it gets swap quotes for crypto assets using native units, distinguishing it from sibling tools like get_quotes that likely use decimal amounts. The verb 'get' and resource 'native quotes' 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 Guidelines4/5

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

Explicitly says when to use: when amounts are in native units. Also notes API key is optional. Could strengthen by explicitly naming alternative tools (e.g., get_quotes for decimal amounts), but the guidance is clear.

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