Skip to main content
Glama

AINDEX

A token's liquidity pools, or every Fables pool

list_pools
Read-only

A token's pools on every venue, most liquid first (20 a page), or with venue "fables" every pool in Fables' registry. Each with its address or Uniswap v4 pool id, pair, venue, liquidity, volume, and price change.

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": "list_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
tokenNo
venueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint), the description adds real behavioral context: results are sorted most-liquid-first and paginated at 20 per page. That is exactly the kind of ordering and page-size disclosure an agent needs to plan calls. It does not state the hard page cap or whether there is a total-count field, which keeps it below a 5.

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?

Two sentences, front-loaded with the primary mode and the alternative, then a compact field list. Almost no waste, though the return-field enumeration could arguably be trimmed since output is fairly self-evident from the resource.

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

Completeness3/5

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

With no output schema and 0% param coverage, the description does describe returned fields, sort order, and page size, which is good. It is still incomplete about default behavior with no parameters, the 5-page limit, and whether results are truncated, which matters for a list tool with all-optional inputs.

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 0%, so the description carries the burden, and it does explain venue="fables" and that pagination runs at 20 per page. But the page ceiling of 5 (max 100 results) and the required 0x address format for token are left to the schema alone, so the compensation for the coverage gap is partial.

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?

The description uses a concrete verb+resource ("A token's pools on every venue") and clearly separates two modes of operation via the venue "fables" flag. It also enumerates the returned fields (address/v4 pool id, pair, venue, liquidity, volume, price change), so an agent knows exactly what it gets. It stops short of naming a sibling it is not, which keeps it from a 5.

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

Usage Guidelines3/5

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

The branching usage is implied well: supply a token to get that token's pools, or supply venue="fables" to get the full registry. However, the schema marks zero required parameters and the description never resolves the ambiguous cases - what happens with no arguments, or with both token and venue set - so the agent must guess those edges.

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