Skip to main content
Glama

spectra_list_pools

Retrieve a list of active Spectra pools on a specified chain, including TVL, implied APY, LP APY, and liquidity data. Sort by metrics, set a minimum TVL, or include expired pools.

Instructions

List all active Spectra pools on a given chain. Returns a summary of each pool including: asset name, maturity, TVL, implied APY, LP APY, pool liquidity, pool reserves (IBT/PT amounts with ratio), IBT APR breakdown (organic vs incentive yield), maturity redemption value, points multipliers, and asset tags.

Metric definitions used across all Spectra tools:

  • PT TVL = value of underlying deposited to mint PTs (pt.tvl in API)

  • Liquidity = AMM pool depth (IBT + PT both sides of the Curve pool, pool.liquidity in API)

  • Implied APY = annualized fixed rate from buying PT at discount

  • IBT APR = variable rate on the underlying vault (labeled APR, not compounded)

Each pool is a Curve StableSwap-NG AMM pair of IBT and PT. LP APY is the yield from providing liquidity to the pool (fees + gauge emissions).

Set include_expired=true to also show recently matured pools (if the API returns them). By default only active (non-expired) pools are shown.

Includes external Merkl campaign APR when available. Output surfaces conditional competing interpretations when data is ambiguous (e.g., high APY with thin liquidity).

For multi-chain discovery, use spectra_get_best_fixed_yields (raw APY ranking) or spectra_scan_opportunities (capital-aware with price impact and looping analysis). Use spectra_get_pool_activity on a specific pool to see recent trading patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesThe blockchain network to query
sort_byNoSort results by this metric (descending)implied_apy
min_tvl_usdNoMinimum TVL in USD to include in results
compactNoIf true, return one-line-per-pool output (much shorter). Use for quick scanning; omit for full details.
include_expiredNoIf true, include recently matured/expired pools in results. Default false (active only).
Behavior4/5

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

No annotations present, so description carries full burden. It details returned metrics, definitions, conditional output, and configuration effects. However, it does not explicitly state read-only nature or rate limits, which would push to 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?

Well-structured with purpose first, then details, then alternative tools. Slightly verbose but efficient for the level of detail needed. Front-loads key info.

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?

No output schema, but description thoroughly explains return values (metrics, definitions, conditional interpretations). Also provides context with sibling tools. Complete for a list tool.

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?

Input schema has 100% coverage with parameter descriptions. The description adds metric definitions but does not significantly enhance per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'List all active Spectra pools on a given chain' with specific verb and resource, and distinguishes from sibling tools like spectra_get_best_fixed_yields and spectra_scan_opportunities.

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?

Explicitly provides when to use this tool vs alternatives, e.g., 'For multi-chain discovery, use spectra_get_best_fixed_yields...' and 'Use spectra_get_pool_activity on a specific pool...'.

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

Install Server

Other Tools

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/Finanzgoblin/spectra-mcp-server'

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