Skip to main content
Glama

swap_via_nattswap

Swap USDC for WBTC or cbBTC on Base via NattSwap (Li.Fi). Get a quote for BTC/USDC exchange on Base, free and without x402.

Instructions

BTC/USDC swap quote on Base (USDC ↔ WBTC/cbBTC) via NattSwap (Li.Fi). Free — no x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromChainYesSource chain id
toChainYesDestination chain id
fromTokenYesSource token address
toTokenYesDestination token address
fromAmountYesAmount in token smallest units
fromAddressYesSender wallet
toAddressYesRecipient wallet
slippageNoSlippage percent
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the tool is a 'swap quote' (safe, read-only) and notes it is free with no x402, but does not detail other behaviors like whether it executes the swap, required permissions, or rate limits. The description is partially transparent but leaves ambiguity about execution vs. quote.

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?

The description is a single, concise sentence that front-loads the most critical information: the swap pair, network, routing, and cost. Every word adds value, with no redundancy.

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 tool has 8 parameters and no output schema, the description is incomplete. It does not explain the return format of the quote, whether it is for cross-chain swaps (despite having fromChain/toChain), or any post-invocation behavior. A more detailed description is needed for full contextual completeness.

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%, so baseline is 3. The description adds no parameter-specific meaning beyond the schema; it only provides an overview. The schema already documents each parameter adequately.

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 the tool provides a BTC/USDC swap quote on Base network, specifying the exact tokens (USDC ↔ WBTC/cbBTC) and the routing via NattSwap (Li.Fi). This specific verb+resource distinguishes it from the sibling 'swap_quote' tool, which may handle different pairs or chains.

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?

The description implies usage for a specific swap route and mentions it is free, but it does not explicitly state when to use this tool over alternatives like 'swap_quote' or provide any exclusion criteria. Usage context is clear but lacks guidance on 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/DIALLOUBE-RESEARCH/hypernatt-terminal'

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