WarpPay402 Gateway

This connector has been deprecated

I used the same url for two different postings.

aerodrome_clamm

Destructive

Allows agents to open, adjust, and rebalance concentrated liquidity ranges on Aerodrome Slipstream ($0.01 USDC)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "aerodrome_clamm"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	CLAMM LP action to perform
`token0`	No	Token 0 address
`token1`	No	Token 1 address

Output Schema

Name	Required	Description
`action`	Yes	Executed CLAMM action
`details`	No	Position details
`success`	Yes	Action status

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 25, 2026

addedInput schema / properties / action / description
```
Added value: +"CLAMM LP action to perform"
```

addedInput schema / properties / token0

Added value: +{
+  "description": "Token 0 address",
+  "type": "string"
+}

addedInput schema / properties / token1

Added value: +{
+  "description": "Token 1 address",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "action": {
+      "description": "Executed CLAMM action",
+      "type": "string"
+    },
+    "details": {
+      "description": "Position details",
+      "type": "object"
+    },
+    "success": {
+      "description": "Action status",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "action"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedSep 17, 2026
- removedInput schema / properties / amount0Desired
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / amount1Desired
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / tickLower
```
Removed value: -{
-  "type": "number"
-}
```
- removedInput schema / properties / tickUpper
```
Removed value: -{
-  "type": "number"
-}
```
- removedInput schema / properties / token0
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / token1
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / tokenId
```
Removed value: -{
-  "type": "string"
-}
```
AddedSep 4, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare destructive=true, idempotent=false, readOnly=false, and openWorld=true, so the safety profile is covered. The description adds domain context about concentrated liquidity ranges, but does not disclose what gets destroyed, whether token approvals are needed, or any rate-limit/auth details.

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 with no wasted words. The parenthetical '$0.01 USDC' is ambiguous but does not significantly bloat the description.

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

Completeness2/5

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

For a multi-action, destructive, open-world LP tool with an output schema and rich annotations, the description is under-specified. It omits the collect action entirely, gives no per-action semantics, and provides no usage guidance to help an agent select the correct action.

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 the schema already documents action, token0, and token1. The description adds no parameter-level meaning, syntax, or constraints beyond the schema baseline.

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 specific domain and operation family: concentrated liquidity range management on Aerodrome Slipstream. It partially maps to the enum actions ('open' ≈ mint, 'adjust' ≈ increase/decrease), but omits collect and does not name or distinguish sibling tools like aerodrome_swap or aerodrome_veaero.

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?

Gives no explicit when-to-use guidance, prerequisites, or alternatives. The reader can infer it is for LP range operations, but nothing tells an agent when to choose this over aerodrome_swap or aerodrome_veaero.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?