LP Pool Check

Find pools with volume and fees

find_active_pools

Read-onlyIdempotent

Use this when the user wants pools across chains or DEXes with recent volume and a fee rate, such as "high fee pools on Base with real volume". All arguments are optional: chains, min_volume_usd_1d (default 50000), min_fee_percent (default 0.05), and limit (default 5, at most 8). Returns each pool's id, volume, TVL, fee rate, 1-day and 7-day fee APR, and an APR flag with its reason, highest 1-day fee APR first. A small pool with a one-day volume spike can rank first, so check tvl_usd and apr_flag before you lead with it, or raise min_volume_usd_1d. It does not read token contracts or the current tick. Call check_pool with a returned pool_id for token flags and the risk checklist.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many pools to return, at most 8. Default 5
`chains`	No	Optional chain names, such as ["base"] or ["ethereum", "arbitrum"]. Supported: ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, solana, zksync, linea, gnosis, scroll, mantle, celo, sonic, or sui. Omit to scan every chain in the index
`min_fee_percent`	No	Minimum swap fee in percent, not a fraction: 0.3 means 0.3%. Read from pool metadata. Default 0.05
`min_volume_usd_1d`	No	Minimum 1-day volume in USD. Default 50000. Raise it, for example to 1000000, to skip small pools with a one-day spike

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`as_of`	Yes	ISO 8601 UTC time of the yields index read, or null when nothing was read
`count`	Yes
`pools`	Yes	Pools ranked by 1-day fee APR, highest first. Check tvl_usd and apr_flag before leading with one
`notice`	Yes
`status`	Yes	unavailable: the yields index could not be read; try again later
`message`	No
`sources`	Yes
`fee_apr_formula`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 13, 2026

changedInput schema / properties / chains / description

Previous value: -"Optional chain names. Omit to scan every chain in the index"New value: +"Optional chain names, such as [\"base\"] or [\"ethereum\", \"arbitrum\"]. Supported: ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, solana, zksync, linea, gnosis, scroll, mantle, celo, sonic, or sui. Omit to scan every chain in the index"

changedInput schema / properties / min_fee_percent / description

Previous value: -"Minimum swap fee in percent, from pool metadata. Default 0.05"New value: +"Minimum swap fee in percent, not a fraction: 0.3 means 0.3%. Read from pool metadata. Default 0.05"

changedInput schema / properties / min_volume_usd_1d / description

Previous value: -"Minimum 1-day volume. Default 50000"New value: +"Minimum 1-day volume in USD. Default 50000. Raise it, for example to 1000000, to skip small pools with a one-day spike"

addedOutput schema / properties / as_of / description

Added value: +"ISO 8601 UTC time of the yields index read, or null when nothing was read"

addedOutput schema / properties / fee_apr_formula
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / pools / description

Added value: +"Pools ranked by 1-day fee APR, highest first. Check tvl_usd and apr_flag before leading with one"

removedOutput schema / properties / pools / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / pools / items / properties

Added value: +{
+  "apr_flag": {
+    "description": "real: steady trading. spike: a short burst, not a steady rate. unconfirmed: no 7-day comparison, do not call it real",
+    "enum": [
+      "real",
+      "spike",
+      "unconfirmed"
+    ],
+    "type": "string"
+  },
+  "apr_flag_reason": {
+    "type": "string"
+  },
+  "chain": {
+    "type": "string"
+  },
+  "exposure": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "fee_rate": {
+    "description": "Swap fee as a fraction, not a percent: 0.003 means 0.3%. Read from pool_meta",
+    "minimum": 0,
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "il_risk": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "pool_id": {
+    "type": "string"
+  },
+  "pool_meta": {
+    "description": "DefiLlama pool label, often the fee tier such as \"0.3%\"",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "project": {
+    "type": "string"
+  },
+  "published_apy": {
+    "properties": {
+      "apy": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "apy_base": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "apy_base_7d": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "apy_reward": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "outlier": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "apy",
+      "apy_base",
+      "apy_reward",
+      "apy_base_7d",
+      "outlier"
+    ],
+    "type": "object"
+  },
+  "symbol": {
+    "type": "string"
+  },
+  "tokens": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "tvl_usd": {
+    "description": "Total value locked in the pool, in USD",
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "windows": {
+    "properties": {
+      "fee_apr_percent_1d": {
+        "description": "Fee APR in percent from 1-day volume: volume x fee_rate x 365 / TVL x 100",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "fee_apr_percent_7d": {
+        "description": "Fee APR in percent from 7-day volume, annualized the same way",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "volume_usd_1d": {
+        "description": "Trading volume over the last day, in USD",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "volume_usd_7d": {
+        "description": "Trading volume over the last 7 days, in USD",
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "volume_usd_1d",
+      "volume_usd_7d",
+      "fee_apr_percent_1d",
+      "fee_apr_percent_7d"
+    ],
+    "type": "object"
+  }
+}

addedOutput schema / properties / pools / items / required

Added value: +[
+  "pool_id",
+  "chain",
+  "project",
+  "symbol",
+  "tvl_usd",
+  "fee_rate",
+  "windows",
+  "published_apy",
+  "tokens",
+  "apr_flag",
+  "apr_flag_reason"
+]

removedOutput schema / properties / sources / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / sources / items / properties

Added value: +{
+  "as_of": {
+    "description": "ISO 8601 UTC time of the yields index read, or null when nothing was read",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "name": {
+    "type": "string"
+  },
+  "note": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / sources / items / required
```
Added value: +[
+  "name",
+  "as_of"
+]
```

addedOutput schema / properties / status / description

Added value: +"unavailable: the yields index could not be read; try again later"

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety burden is covered. The description goes further by disclosing output ordering (highest 1-day fee APR first) and a real pitfall — small pools with a one-day spike can rank first — with a concrete mitigation.

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?

Front-loaded with the usage trigger and only five sentences, all informative. The middle sentence re-listing every argument with its default duplicates the schema, which is the one minor waste in an otherwise tight definition.

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?

An output schema exists, yet the description still sketches the return shape, names the ranking, warns about a ranking artifact, and routes to check_pool for follow-up. Nothing an agent needs to call it correctly is missing.

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%, so the schema itself documents every parameter; the description still adds value by restating defaults and giving tuning advice ('raise min_volume_usd_1d... to skip small pools with a one-day spike'). Slight redundancy with the schema keeps this from a 5.

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?

States a specific verb and resource (finds pools across chains/DEXes filtered by volume and fee rate) and immediately distinguishes itself from the sibling check_pool, which it says handles token flags and risk. An agent can select this without opening another schema.

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

Usage Guidelines5/5

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

Opens with an explicit when-to-use trigger ('when the user wants pools across chains or DEXes with recent volume and a fee rate'), gives a concrete example query, and names both the alternative (check_pool) and an exclusion ('does not read token contracts or the current tick').

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

All LP Pool Check 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.