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.
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.
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": "build_swap_transaction", "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
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.
The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.
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.
build_lp_create_position
Build the calldata to create a new V3 or V4 LP position. POSTs to `/v1/lp/create` with the wallet, pool params, tick range, and amounts. Returns the raw `/lp/create` response — the unsigned transaction fields (`to`, `data`, `value`, `gasLimit`) the caller's wallet signs and submits. Pairs with `build_lp_increase_position`, `build_lp_decrease_position`, and `build_lp_claim_fees` to manage the position over its lifetime. 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.