Skip to main content
Glama
fletch-now

fletch-mcp

Official
by fletch-now

DEX pools for one asset

pools

Find a ticker's trading venues across Uniswap V3 and V4, ranked by dollar depth, with price, liquidity, fee, swaps, volume, and the Chainlink premium venue.

Instructions

The pools that trade a ticker, deepest first in dollars, on every DEX the registry reads: venue (uniswap_v4 or uniswap_v3), price in the quote and in dollars, depthUsd, liquidity, fee, hooks, swaps and volume, plus the pool used for the asset's premium against the Chainlink feed, which is the deepest pool in dollars of any venue. depthUsd is how many dollars of the quote token it takes to move the pool's price by 1% — a ceiling, since a move that leaves the position's range runs out of liquidity first, and not the pool's token balance; liquidity is Uniswap's raw in-range L, not a dollar figure, and compares two pools only when they hold the same pair. swaps24h and volumeUsd24h cover the current UTC day and the one before it, and are null for a pool discovered inside that window, whose earlier swaps the scan never read. A v4 pool is an id inside the one PoolManager and has no address of its own; a v3 pool is a contract and carries poolAddress. discovery says how far each venue's pool scan has read: while readingHistory is true a pool in blocks not yet reached is missing from the list, and while scanned is false that venue has not been read at all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTicker, e.g. TSLA

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers substantial transparency. It explains the exact meaning of depthUsd as a ceiling, clarifies that liquidity is raw in-range L and not a dollar figure, notes null swaps/volume for newly discovered pools, explains v4 vs v3 addressing, and defines discovery states. These are non-obvious behaviors essential to interpreting results.

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?

The description is long, but every sentence carries substantive meaning about field semantics, edge cases, or discovery behavior. The main outcome and ordering are front-loaded, followed by caveats. It could be broken into shorter sentences or bullets for readability, but it is not padded with filler.

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 data-rich tool with no output schema, the description is remarkably complete. It specifies the fields returned, the units and semantics of ambiguous metrics, time-window behavior for swaps and volume, v4/v3 structural differences, and discovery-state caveats. The one required parameter is trivially documented, so nothing essential is missing for correct invocation and interpretation.

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?

The input schema already documents the only parameter, symbol, with a clear example (TSLA), and coverage is 100%. The description adds context that the symbol is a ticker used to find trading pools, but it does not need to add more because the schema is sufficient for this single-parameter tool.

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 names a specific resource (DEX pools for a ticker) and a precise shaping (deepest first in dollars, across all venues the registry reads). It enumerates the returned fields and the special pool used for premium, which makes the tool's purpose unmistakable and distinguishes it from asset-level siblings like get_asset or dex_venues.

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

Usage Guidelines4/5

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

The description clearly establishes when to use the tool: to obtain pools trading a given ticker, sorted by dollar depth, across every venue. It does not explicitly enumerate exclusions or alternatives among the sibling tools, but the domain and scope are stated precisely enough that an agent can infer the appropriate context.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fletch-now/fletch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server