Skip to main content
Glama

pool_snapshot

Read-onlyIdempotent

Get a cached snapshot of top DeFi liquidity pools. Filter by protocol (e.g. "uniswap-v3"), chain (e.g. "ethereum"), or token symbol (e.g. "ETH"). Returns TVL, APY, 24h volume, IL risk, and registry enrichment. Data refreshed every 15 minutes.

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

Input Schema

NameRequiredDescriptionDefault
poolNoFilter by specific pool address or DeFi Llama pool ID
chainNoFilter by chain, e.g. "ethereum", "base", "arbitrum"
limitNoMax results (1-100)
orderNoSort orderdesc
tokenNoFilter pools containing this token symbol, e.g. "ETH", "USDC"
offsetNoPagination offset
sortByNoSort fieldtvl
protocolNoFilter by protocol name, e.g. "uniswap-v3", "curve", "aave"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral facts beyond that: the data is cached and stale up to 15 minutes, and it enumerates the returned fields including registry enrichment. It does not mention result caps or how ordering interacts with pagination beyond what the schema states.

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

Conciseness5/5

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

Three tight sentences: purpose first, filtering second, return payload and refresh cadence last. Every sentence carries information and there is no filler or repetition.

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

Completeness4/5

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

With 8 optional parameters, 100% schema coverage, and no output schema, the description helpfully compensates by listing the returned metrics and the 15-minute freshness window. It omits default ordering/pagination behavior, but those are documented in the schema, so the definition is essentially complete for correct invocation.

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 coverage is 100% and every parameter carries its own description and examples, so the schema does the heavy lifting. The description restates the protocol/chain/token filters with the same example values the schema already supplies, adding little semantic meaning beyond that. Baseline 3 applies.

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?

States a specific verb and resource ("Get a cached snapshot of top DeFi liquidity pools") and names the filterable dimensions, so an agent can tell it apart from token-centric siblings like token_intel or token_risk_metrics. It stops short of explicitly naming which sibling handles overlapping pool/liquidity questions.

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?

Usage is only implied: the examples of protocol/chain/token filters suggest when this table-scan tool is appropriate, but there is no explicit "use this when / use X instead" routing against alternatives such as risk_batch, token_compare, or token_research. An agent must infer that this is the discovery layer before drilling into per-token tools.

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.