Skip to main content
Glama

mv_scan_curator_opportunities

Scan Spectra and Pendle chains for top yield opportunities sized to your capital, with capital-aware price impact and cross-protocol matching.

Instructions

Scan all Spectra AND Pendle chains for the best yield opportunities, sized to your capital. Cross-protocol scanner designed for MetaVault curators who can allocate to either protocol.

Unlike spectra_scan_opportunities (Spectra-only), this tool includes Pendle markets with:

  • Capital-aware price impact for BOTH protocols

  • Maturity-aware cross-protocol matching (same underlying + similar expiry)

  • Morpho looping analysis for Spectra PTs (Pendle looping in future phase)

  • Unified ranking by effective APY across both protocols

  • External Merkl campaign APR for both protocols (incentive programs beyond native yield)

  • Protocol tags ([Spectra] vs [Pendle]) and cross-protocol match indicators

Unlike spectra_get_best_fixed_yields or pendle_list_markets, this tool computes effective APY at YOUR capital size — a high-APY pool with thin liquidity may be useless at your scale.

The ranking can disagree with spectra_scan_opportunities because it includes a different opportunity set (Pendle markets). This disagreement is intentional — both tools measure different things.

Use mv_compare_yield for detailed head-to-head on a specific chain. Use spectra_model_metavault to model blended Spectra+Pendle MetaVault allocation. Use spectra_get_curator_dashboard for operational monitoring of an existing MetaVault.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capital_usdYesHow much capital (in USD) to deploy
asset_filterNoOptional: filter by underlying asset symbol (e.g., 'USDC', 'ETH')
min_tvl_usdNoMinimum pool TVL in USD (default $10,000)
min_liquidity_usdNoMinimum pool liquidity in USD (default $5,000)
max_price_impact_pctNoFilter out pools where entry impact exceeds this % (default 5)
top_nNoNumber of top results to return (default 15, max 50)
include_loopingNoWhether to check Morpho looping for Spectra PTs (default true)
compactNoIf true, return one-line-per-opportunity output (much shorter).
ve_spectra_balanceNoYour veSPECTRA token balance. Computes Spectra boost for LP APY.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the tool's cross-protocol nature, capital-aware computation, inclusion of price impact, maturity matching, Morpho looping, Merkl campaigns, and protocol tags. It also notes potential ranking disagreements. Could be more explicit about being read-only, but overall transparent.

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 bullet points and clear comparisons. Front-loaded with purpose. Slightly long due to future-phase notes, but overall efficient and informative.

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?

Comprehensively covers the tool's role, differentiation, and usage context. Despite no output schema, it describes the output nature (ranked list, one-line compact option). All relevant aspects are addressed.

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% with clear parameter descriptions. The tool description adds context about capital-aware behavior and compact output but does not add new parameter-level semantics beyond what the schema provides. 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?

The description clearly states the tool scans both Spectra and Pendle chains for best yield opportunities sized to capital. It explicitly contrasts with Spectra-only and Pendle-only siblings, and highlights cross-protocol matching, capital-aware impact, and unified ranking.

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?

Provides explicit when-to-use guidance: contrasts with spectra_scan_opportunities, spectra_get_best_fixed_yields, and pendle_list_markets. Also lists alternative tools for specific use cases (mv_compare_yield, spectra_model_metavault, spectra_get_curator_dashboard).

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