get_swappable_tokens
List the destination bridge chains a given token on a given chain can be swapped or bridged into. The Uniswap API takes the source `tokenIn` and `tokenInChainId` as required query parameters and returns the destinations the source token is supported on. The integration spec for this subcategory described a `chain` / `includeCrossChain` shape, but the underlying API does not accept that shape; the tool follows the actual API contract so the response is real data, not a 400.
List the destination bridge chains a given token on a given chain can be swapped or bridged into. The Uniswap API takes the source tokenIn and tokenInChainId as required query parameters and returns the destinations the source token is supported on.
Input
The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.
Calling it
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "get_swappable_tokens", "arguments": {} }
}Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.
Notes
The integration spec for this subcategory described a chain / includeCrossChain shape, but the underlying API does not accept that shape; the tool follows the actual API contract so the response is real data, not a 400.
The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.
check_approval
Check whether a wallet has the required token approval (Permit2 or router allowance) to swap a given amount on a chain. Returns the raw `/check_approval` response, with an `approval` key that is `null` when the wallet is good to go, or a transaction the caller must sign when an approval is needed. Pairs with `get_swap_quote`: an agent should call this before quoting so the approval path is known up front.
build_swap_transaction
Build the calldata for a swap transaction against the Uniswap protocols. POSTs to `/v1/swap` with the same fields as `get_swap_quote` plus the signed Permit2 payload. Returns the raw `/swap` response — the unsigned transaction fields (`to`, `data`, `value`, `gasLimit`) the caller's wallet signs and submits. The Putty dashboard signs through the user's Privy embedded wallet in the sign-request modal; external agents sign with their own wallet. The tool never holds a signing key.