WarpPay402 Gateway

by com.warppay402.api

Overview Discussions Admin

This connector has been deprecated

I used the same url for two different postings.

get_aerodrome_yields

Read-onlyIdempotent

Fetch live Aerodrome DEX pool yields, APYs, TVL, Base EVM pool addresses, and DefiLlama UUIDs ($0.003 USDC)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_aerodrome_yields"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`epoch`	Yes	Aerodrome weekly epoch Unix timestamp
`success`	Yes	Query status
`protocol`	No	Protocol name
`timestamp`	No	ISO timestamp
`blockNumber`	Yes	Base Mainnet block height
`topYieldPools`	Yes	Top Aerodrome pools ranked by TVL/APY

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / minTvlUsd

Removed value: -{
-  "description": "Minimum TVL in USD threshold to filter pools",
-  "type": "number"
-}

Changed4 schema fields changedSep 26, 2026

addedOutput schema / properties / blockNumber

Added value: +{
+  "description": "Base Mainnet block height",
+  "type": "integer"
+}

addedOutput schema / properties / epoch

Added value: +{
+  "description": "Aerodrome weekly epoch Unix timestamp",
+  "type": "integer"
+}

addedOutput schema / properties / timestamp

Added value: +{
+  "description": "ISO timestamp",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "success",
-  "topYieldPools"
-]New value: +[
+  "success",
+  "blockNumber",
+  "epoch",
+  "topYieldPools"
+]

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / minTvlUsd

Added value: +{
+  "description": "Minimum TVL in USD threshold to filter pools",
+  "type": "number"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "protocol": {
+      "description": "Protocol name",
+      "type": "string"
+    },
+    "success": {
+      "description": "Query status",
+      "type": "boolean"
+    },
+    "topYieldPools": {
+      "description": "Top Aerodrome pools ranked by TVL/APY",
+      "type": "array"
+    }
+  },
+  "required": [
+    "success",
+    "topYieldPools"
+  ],
+  "type": "object"
+}

AddedSep 1, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so safety is covered. The description adds behavior annotations do not: that data is "live" and that each call costs $0.003 USDC — a genuinely decision-relevant cost disclosure for an agent.

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 dense sentence, front-loaded with the verb and resource, with the price tag appended. Slightly redundant in enumerating return fields that the output schema already defines, but nothing is wasted.

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?

With an output schema present, the description needn't explain return values, and it covers source, liveness and cost. The only real gap is the absence of comparison guidance against the crowded aerodrome sibling set.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The listed output fields add a little context but the output schema already carries return semantics.

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?

Specific verb ("Fetch") plus a narrow resource ("Aerodrome DEX pool yields") and an explicit enumeration of returned data (APYs, TVL, pool addresses, DefiLlama UUIDs). An agent can distinguish it from aerodrome_swap or aerodrome_veaero, though it never names those siblings or contrasts scopes.

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?

No guidance on when to prefer this over the many sibling aerodrome_* tools, nor any prerequisites or exclusions. Usage must be inferred entirely from the resource name.

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?