WarpPay402 Gateway

aerodrome_swap

Destructive

Executes low-slippage token swaps directly via Aerodrome Finance Router on Base Mainnet ($0.01 USDC)

Input Schema

TableJSON Schema

Name	Required	Description
`tokenIn`	Yes	Input token contract address on Base
`amountIn`	Yes	Amount of input token to swap in human units
`isStable`	Yes	Whether swap route uses stable or volatile pool
`tokenOut`	Yes	Output token contract address on Base
`decimalsIn`	Yes	Input token decimal precision

Output Schema

TableJSON Schema

Name	Required	Description
`success`	Yes	Execution status
`quotedAmountOut`	No	Received output token amount
`transactionHash`	Yes	On-chain transaction hash on Basescan

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 25, 2026

addedInput schema / properties / amountIn / description

Added value: +"Amount of input token to swap in human units"

addedInput schema / properties / decimalsIn / description
```
Added value: +"Input token decimal precision"
```

addedInput schema / properties / isStable / description

Added value: +"Whether swap route uses stable or volatile pool"

addedInput schema / properties / tokenIn / description

Added value: +"Input token contract address on Base"

addedInput schema / properties / tokenOut / description

Added value: +"Output token contract address on Base"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "quotedAmountOut": {
+      "description": "Received output token amount",
+      "type": "string"
+    },
+    "success": {
+      "description": "Execution status",
+      "type": "boolean"
+    },
+    "transactionHash": {
+      "description": "On-chain transaction hash on Basescan",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "transactionHash"
+  ],
+  "type": "object"
+}

AddedSep 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered and the description does not contradict it. The description adds only 'low-slippage' and the price note; it omits any warning that swaps are irreversible, that token approvals may be required, or how slippage is actually controlled.

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?

A single front-loaded sentence that names the action, the router, and the network without padding. The trailing '($0.01 USDC)' is cryptic and slightly detracts, keeping it just short of a 5.

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

Completeness3/5

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

An output schema exists, so return values need not be described. However, for a destructive, non-idempotent swap tool the description leaves key operational context unstated: approval/allowance requirements, absence of slippage-tolerance or deadline controls, and no routing guidance versus its aerodrome_clamm sibling.

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 each of the five parameters is already documented inline; that sets the baseline at 3. The description adds no parameter meaning beyond the schema, and notably does not explain that no slippage-tolerance or deadline parameter exists despite the 'low-slippage' claim.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: executes token swaps via the Aerodrome Finance Router on Base Mainnet. It implies a router-level (spot pool) swap, but does not explicitly distinguish itself from the sibling aerodrome_clamm, so an agent must still infer when this versus the CLAMM tool is appropriate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, despite several closely related Aerodrome siblings (aerodrome_clamm, aerodrome_veaero). The parenthetical '($0.01 USDC)' is unexplained and reads more like an incidental cost note than usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WarpPay402 Gateway tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?