Skip to main content
Glama

spectra_list_expiring_pools

List pools nearing maturity across Spectra chains, grouped by urgency. Includes successor status, gauge info, and a readiness assessment to plan rollover or migration.

Instructions

Scan all Spectra chains for pools approaching maturity.

Returns pools expiring within the specified threshold (default 21 days / 3 weeks), grouped by urgency level. Designed for operators who need lead time to:

  • Create follow-up pools with new maturities

  • Submit gauge proposals for successor pools

  • Plan LP migration and rollover strategies

  • Coordinate with IBT protocol teams

Each result includes the PT address, IBT address, chain ID, underlying asset, TVL, and current implied APY — everything needed to plan the successor pool.

Automatically cross-references each expiring pool's IBT against all active pools to flag whether a successor pool (same IBT, later maturity) already exists or needs to be created.

Gauge status is fetched from the governance voting-incentives API. A pool address present in that endpoint has a gauge (even if it currently has 0 votes / 0 emissions). Gauge API failure is best-effort — gauge status shows as unknown, does not block results.

Per-pool readiness assessment combines successor status, gauge status, and timing: OK: Successor deployed with gauge and seeded CAUTION: Successor exists but missing gauge or low TVL; or no successor but >7d runway WARNING: No successor and ≤7d; or successor without gauge and ≤14d

Urgency (time-based) and readiness (action-based) are independent dimensions. A pool can be ALERT urgency (21d runway) but WARNING readiness (no successor at all). The Operator Checklist section groups required actions by type:

  • Deploy successor pool: IBTs with no active successor

  • Submit gauge proposal: successors that exist but lack a gauge

  • Ready for migration: successors with gauge and adequate TVL

Urgency levels: CRITICAL (≤7 days): Immediate action required WARNING (≤14 days): Start preparations now ALERT (≤21+ days): Plan ahead

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

Use mv_plan_rollover on a specific MetaVault for automated rollover candidate discovery. Use spectra_get_yield_curve to see what maturities already exist for the same underlying. Use spectra_list_pools to check if a successor pool has already been created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threshold_daysNoWarning threshold in days before maturity (default 21 = 3 weeks). Pools expiring within this window are returned.
chainNoRestrict to a single chain. Omit to scan all chains.
min_tvl_usdNoMinimum TVL in USD to include (default 0 = show all)
compactNoOne-line-per-pool output for quick scanning. Omit for full details.
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses behavioral traits: gauge status is fetched 'best-effort' and 'does not block results'; urgency and readiness are independent dimensions; default shows active pools only; output includes operator checklist. No contradictions.

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 relatively long but well-structured with clear sections (urgency levels, readiness assessment, operator checklist). Every sentence adds value, though it could be slightly more concise. Structure is front-loaded with purpose and use cases.

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 complex tool scanning multiple chains with cross-referencing and multiple output dimensions, the description is complete. It covers parameters, edge cases (best-effort gauge), output format, and relationships between urgency and readiness. No output schema, but description explains results adequately.

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

Parameters4/5

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

Schema coverage is 100%, so baseline 3. The description adds meaning beyond parameter descriptions by explaining the output fields, urgency levels, readiness assessment, and the implication of thresholds. It does not repeat schema but enriches context.

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 starts with a clear verb+resource: 'Scan all Spectra chains for pools approaching maturity.' It specifies the resource (pools) and action (scan for expiring). It distinguishes itself from siblings by listing alternative tools like mv_plan_rollover, spectra_get_yield_curve, and spectra_list_pools.

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 states when to use this tool versus alternatives: 'Use mv_plan_rollover on a specific MetaVault for automated rollover candidate discovery. Use spectra_get_yield_curve to see what maturities already exist for the same underlying. Use spectra_list_pools to check if a successor pool has already been created.' It also provides context for operators and specifies default parameters.

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