Skip to main content
Glama

AINDEX

A Uniswap v4 or Fables pool, ready to provide liquidity

get_v4_pool
Read-only

By pool id: the key, price, tick and spacing, ready-made ranges with the value split per side, volume, TVL, the fee actually charged, a pool-wide fee APR after Fables' claim fee, Merkl incentives and Fables' points and weekly pot.

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": {
      "poolId": "<poolId>"
    },
    "name": "get_v4_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds substantive behavioral context by enumerating what data is returned—pool state, ready-made ranges with split values, volume, TVL, actual fee, fee APR after Fables' claim fee, Merkl incentives, points, and weekly pot—which helps an agent understand the response. It does not cover error behavior or pagination, but given the annotation coverage this is a strong addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single long sentence with a dense list of return fields. It is front-loaded with 'By pool id' and contains no obvious filler, but the run-on structure makes it harder to scan than a short purpose statement plus a structured field list.

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?

For a one-parameter read-only lookup with no output schema, the description correctly attempts to explain return contents by enumerating many fields. However, it omits parameter meaning and any usage context, and without an output schema the list may still leave an agent unsure of the exact response shape. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, poolId, with 0% schema description coverage; the schema only supplies a regex pattern. The description says 'By pool id' and nothing else about the parameter—no explanation of its format beyond the pattern, where to obtain it, or what a valid id represents. With the schema doing minimal work, the description fails to compensate.

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 name, title, and opening phrase 'By pool id' clearly establish a Uniswap v4 or Fables pool lookup, and the description enumerates the returned data fields (price, tick, ranges, volume, TVL, fee APR, incentives). However, it lists outputs rather than stating a specific retrieval verb, so the purpose is clear but not crisply framed.

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 is provided on when to use this tool versus siblings such as get_token_market or get_lighter_market, and no prerequisites or exclusions are stated. 'By pool id' implies the input but does not tell an agent when to choose this lookup over alternatives.

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