Skip to main content
Glama

pancakeswap_fee_tiers

Read-only

Measure which PancakeSwap fee tier of a pair actually pays liquidity providers, to decide WHERE to put liquidity. Use it before adding liquidity to a pair; once the pool is chosen use pancakeswap_range_plan for the price range, for a position you already hold use pancakeswap_position_look, and for a swap (not liquidity) use pancakeswap_best_route. Pass a token to compare all its pools against its main quote, or a pool address to pin the exact pair. A pair lives in up to five pools at once — V2 at 0.25% and V3 at 0.01%, 0.05%, 0.25% and 1.00% — and every source ranks them by the money already parked in them, which does not say which one pays. This measures each tier over a live window: swaps, turnover, the fees the pool actually paid out, and those fees per $1,000 of capital — over TWO denominators. The first is everything the pool holds, which is what every interface shows. The second is the capital standing within 2% of the current price, reconstructed by walking the tick book of the pool itself, because concentrated liquidity parked far from the price earns nothing and a new dollar only competes with the capital that is at the price. The two rankings disagree often, and both are returned. It also names tiers holding real money that did not trade at all. Measured, never annualised: the window is about an hour of chain and is reported with the answer. The same token asked again within 60 seconds gets the same measurement from the edge cache (cache.hit, cache.age_seconds). Read-only, free, no key; a tier whose pool could not be read is listed in tiers_unreadable and comparison_complete says whether every tier was measured.

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": {
      "address": "<address>"
    },
    "name": "pancakeswap_fee_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA BSC token address (all of its PancakeSwap pools against its main quote are compared), or one PancakeSwap pool address to pin that exact pair; 0x + 40 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / address / examples
      Added value: +[
      +  "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"A BSC token address, or a PancakeSwap pool address to pin the pair"New value: +"A BSC token address (all of its PancakeSwap pools against its main quote are compared), or one PancakeSwap pool address to pin that exact pair; 0x + 40 hex"
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description adds substantial context beyond them: a ~1-hour live measurement window, no annualisation, a 60-second edge cache with cache.hit/cache.age_seconds, and two competing rankings (total capital vs capital within 2% of price). It also discloses partial-failure behavior via tiers_unreadable and comparison_complete. The only gap is that the exact return shape is described qualitatively rather than concretely, but with no output schema this is mostly covered.

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 purpose and routing before the mechanics, and nearly every sentence carries decision-relevant information. It is dense and somewhat long, with a few rhetorical asides ('which does not say which one pays') that could be trimmed without losing substance.

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?

For a one-parameter, no-output-schema tool, the description covers the return semantics (two rankings, per-$1,000 fee figures, unreadable tiers, completeness flag), the measurement caveats, and caching behavior. An agent has enough to call it and interpret the result correctly.

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% and the single parameter's schema text already explains the token-vs-pool-address interpretation. The description's 'Pass a token to compare all its pools ... or a pool address to pin the exact pair' largely restates the schema, adding emphasis rather than new meaning, so the baseline 3 applies.

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: measuring which PancakeSwap fee tier of a pair actually pays LPs, framed as 'decide WHERE to put liquidity.' It explicitly contrasts itself with three named siblings (pancakeswap_range_plan, pancakeswap_position_look, pancakeswap_best_route), so an agent can route without opening any 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?

Gives an explicit sequencing rule ('use it before adding liquidity'), then names the alternative for each adjacent task: range planning, inspecting an existing position, and swaps. The single-parameter disambiguation (token vs pool address) is also framed as a usage choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources