Skip to main content
Glama

spectra_get_curator_dashboard

Aggregate MetaVault health, position status, depositor flows, fee revenue estimates, and alerts into a single operational dashboard for curators.

Instructions

Operational dashboard for MetaVault curators.

Aggregates vault health, position status, depositor flows, fee revenue estimates, and actionable alerts into a single view. Designed for curators managing live MetaVaults who need a quick operational overview.

Returns:

  • Vault health: TVL with unallocated ratio (undeployed capital AFTER subtracting external positions — shown when >5%), Status label for non-VISIBLE vaults, live APY with optional 30d avg suffix and APY composition (base vs incentives), share price

  • APY 4-number breakdown when live-vs-30d delta ≥ 0.5pp: shows base+incentive decomposition for both snapshots WITHOUT asserting causality (agents draw their own conclusions from the numbers)

  • Position status: each active PT position with maturity countdown, APY, and size. Positions approaching maturity are flagged (!!!=14d, !!=30d)

  • External Positions: value held OUTSIDE Spectra LP structure (avant avUSDx-burn redemption-in-flight, pendle LP on other protocols). Rendered per-protocol with graceful fallback for unknown protocols

  • Capital State decomposition line: when ≥1 of {expired-stuck, external} buckets populated, emits a single line showing deployed/expired-stuck/ external/unallocated as % of TVL

  • Depositor flows: epoch-by-epoch net inflows/outflows with trend analysis

  • Fee revenue: estimated annual curator fee revenue (snapshot projection)

  • Action items: auto-generated alerts including [UNALLOC] (softened when external capital coexists), [STATUS] (HIDDEN vaults), [PENDLE-EXT URGENT/UPCOMING/EXPIRED] (external Pendle maturity), [EXPIRED] / [URGENT] / [SOON] / [UPCOMING] (Spectra LP maturity), [OUTFLOWS], [BRIDGE], [INCENTIVE], [PENDLE ROLLOVER]

Pool allocations show each position as a % of total vault TVL (e.g., "37.1% | $236K"), sorted by size, with protocol tags ([Spectra]/[Pendle]/[Unknown]) on each position. Unallocated liquidity is shown separately (and excludes capital deployed in external positions — labeled as "unallocated" to distinguish from "idle"). When the API doesn't provide LP balance data for a position, it shows "?%".

Cross-chain positions: MetaVault positions may live on a different chain than the MetaVault itself (e.g., Base MetaVault → Avalanche pools via CCTP bridge). Pool addresses in positions are on the position's chain, not the MetaVault's home chain.

Epoch flows: Derived from asset snapshots and rate changes. Yield accrual is estimated from share rate deltas — actual yield may differ. Use share price trend to corroborate.

Requires chain + metavault_address. Use spectra_list_metavaults to discover addresses. Use spectra_model_metavault for leverage modeling after reviewing the dashboard. Use spectra_get_pool_activity on specific pool addresses for trading pattern analysis. Use spectra_get_address_activity on the curator's EOA for cross-pool curator activity.

When verify_externals=true (off by default), each avant external position is probed on Avalanche's RequestsManager — confirms state (CREATED/COMPLETED/CANCELLED), provider attribution, on-chain amount (with PPM tolerance for API rounding), global counter, and pause flag. A [chain-truth ✓/⚠/✗] line is appended under each avant position. Per-order failures degrade gracefully and never poison sibling positions or block the dashboard. Pendle externals are NOT yet probed in this slice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesThe blockchain network where the MetaVault lives.
metavault_addressYesThe MetaVault contract address. Use spectra_list_metavaults to discover addresses.
curator_fee_pctNoCurator performance fee as % of vault yield (default 10%). Used for fee revenue estimation.
verify_externalsNoVerify each externalPosition on its target chain (Theme E). Today probes Avant burn orders against Avalanche RequestsManager — confirms state (CREATED/COMPLETED/CANCELLED), provider attribution, on-chain amount, queue counter, and pause flag. Off by default — adds RPC latency and pressure on each external. Use when an avant external is load-bearing for a curator decision (large redemption-in-flight, stuck claim, suspected stale API). Per-position failures degrade to a [chain-truth ✗] line but never poison sibling positions. Pendle external verification is a separate next-session slice. Dissolution: if telemetry shows zero verify_externals=true invocations within 60 days of ship, the flag is fossil — fold the verifier into list-mode default or remove.
Behavior5/5

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

With no annotations, the description fully bears the burden. It exhaustively discloses behaviors: estimated yield, cross-chain handling, default values, and the verify_externals parameter's performance cost and degradation behavior. Caveats like 'actual yield may differ' ensure realistic expectations.

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 lengthy but well-structured with clear sections (Returns: with sub-bullets, important notes on cross-chain positions and epoch flows). Every sentence provides value, and key information is front-loaded (purpose, target user, required params). No redundancy.

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?

Given the tool's complexity and lack of output schema, the description covers all aspects: return fields (vault health, position status, external positions, capital decomposition, depositor flows, fee revenue, action items), edge cases (flagging maturities, unknown protocols, missing LP balance, cross-chain positions), and limitations (estimated yield, verify_externals performance impact).

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?

Input schema coverage is 100%, so baseline is 3. The description adds meaning beyond schema by explaining the purpose of curator_fee_pct (for fee estimation) and verify_externals (verification details and when to use). It also clarifies chain and metavault_address usage.

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 clearly defines the tool as an operational dashboard for MetaVault curators, listing aggregated data like vault health, position status, depositor flows, etc. It distinguishes itself from sibling tools like spectra_list_metavaults and spectra_model_metavault by targeting a quick operational overview.

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

Usage Guidelines4/5

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

The description specifies the target user (curators managing live MetaVaults) and provides explicit pointers to alternative tools for related tasks (e.g., spectra_list_metavaults for addresses, spectra_model_metavault for leverage modeling, spectra_get_pool_activity for trading patterns). It lacks explicit 'when not to use' but context is clear.

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