Skip to main content
Glama

swap

Exchange native ETH for $CPU or sell $CPU for ETH on the Uniswap v4 pool. Enter amount and slippage; the transaction is executed on-chain.

Instructions

Swap between native ETH and $CPU on the game token pool (Uniswap v4), in either direction: sell: "ETH" buys $CPU, sell: "CPU" sells it for ETH. amount is how much of the sold token to spend. Preview the result first with quote_swap. The swap is exact-input: you spend amount and receive at least the quoted output minus slippage (a percent, e.g. 0.5 = 0.5%). Selling $CPU auto-approves it (via Permit2) once before the first swap; the trade is submitted on-chain and this waits for confirmation. A 1% pool fee applies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sellYesToken to spend: ETH (to buy $CPU) or CPU (to sell for ETH).
amountYesAmount of the `sell` token to spend, as a decimal string (e.g. "0.5"). 18 decimals.
slippageNoMax slippage as a percent (e.g. 0.5 = 0.5%); the floor on what you receive. Default 0.5.
Behavior5/5

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

Discloses exact-input behavior, on-chain submission with confirmation wait, 1% pool fee, and one-time auto-approval via Permit2 for CPU. No annotations provided, so description carries full burden and meets it well.

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?

Single paragraph effectively communicates essential details without excess. Could be slightly more structured, but every sentence adds value.

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

Completeness5/5

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

Covers mechanism, prerequisites, behavior, and edge cases (auto-approval, fee). Adequate for an agent to decide and invoke correctly despite no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds context: sell parameter direction, amount decimal string with 18 decimals, slippage as percent with default. Adds value beyond schema.

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 the tool swaps between native ETH and $CPU on a Uniswap v4 pool, specifying direction via the 'sell' parameter. Distinguishes itself from sibling 'quote_swap' which is for previewing.

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 advises to preview with 'quote_swap' first. Describes direction logic and auto-approval for CPU. Lacks explicit when-not-to-use but provides enough context for correct invocation.

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/sodiqit/cpu-game-mcp'

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