WarpPay402 Gateway

This connector has been deprecated

I used the same url for two different postings.

aerodrome_swap

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

A4/5.0

Behavior4/5

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

Annotations already indicate a mutating, non-idempotent operation, and the description adds useful behavioral context: direct Router execution, Base Mainnet, low-slippage intent, and a $0.01 USDC cost/fee signal. It does not contradict the annotations, but it could have disclosed approval/gas requirements for a swap execution.

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?

A single dense sentence that front-loads the core action, route, and network, then adds the cost signal as a compact parenthetical. No filler or redundant restatement of the tool name.

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

Completeness4/5

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

For a mutating on-chain swap tool, the description covers the main context: what executes, where, and at what cost. With full parameter documentation and an output schema present, the remaining gaps are minor, such as wallet-approval and slippage-enforcement details.

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 coverage is 100%, so every parameter is already documented in the input schema. The description does not add parameter-level semantics beyond the schema, matching the baseline expectation when the schema carries the full load.

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?

The description uses a specific verb ('Executes') and names the resource ('token swaps') and mechanism ('via Aerodrome Finance Router on Base Mainnet'). This clearly distinguishes it from sibling tools like aerodrome_clamm or get_aerodrome_yields, even without a title.

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 the tool is for performing token swaps, but it does not explicitly state when to use this over related Aerodrome tools or when not to use it. There are no named alternatives or exclusion conditions, leaving some routing judgment to the agent.

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?