Skip to main content
Glama

spectra_get_best_fixed_yields

Scan all Spectra chains and retrieve top fixed-rate yield opportunities ranked by implied APY. Filter by asset, minimum TVL, liquidity, and number of results.

Instructions

Find the best fixed-rate yield opportunities across all Spectra chains. Scans all supported networks and returns the top opportunities ranked by implied APY. Filters by asset type if specified.

Important: This ranks by raw implied APY without considering your capital size or pool liquidity. These rankings will often disagree with spectra_scan_opportunities (which ranks by effective APY after entry cost). That disagreement is intentional -- raw APY reflects the pool's headline rate while effective APY reflects what you actually capture at your capital size. Neither ranking is "correct" -- they measure different things. Use both to develop conviction about which pools genuinely serve your strategy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_filterNoOptional: filter by underlying asset symbol (e.g., 'USDC', 'ETH', 'GHO')
min_tvl_usdNoMinimum pool TVL in USD (default $10,000)
min_liquidity_usdNoMinimum pool liquidity in USD (default $5,000)
top_nNoNumber of top results to return (default 10, max 50)
compactNoIf true, return one-line-per-opportunity output (much shorter). Use for quick scanning; omit for full details.
Behavior4/5

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

Discloses that rankings are by raw APY without considering capital size or liquidity, and explains the different focus from the sibling tool. No annotations provided, so description carries full burden.

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?

Three paragraphs, front-loaded with main purpose. Additional explanation of ranking trade-offs is useful but could be slightly trimmed. No redundant content.

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?

Covers purpose, parameters, and differentiation from sibling. No output schema, but description implies return of top opportunities ranked by APY. Missing details on actual response format, but sufficient for a read-only query 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?

Schema coverage is 100% so baseline is 3. Description adds context for compact parameter ('use for quick scanning') and states asset filter, but does not substantially enhance understanding beyond schema.

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?

Clearly states 'Find the best fixed-rate yield opportunities across all Spectra chains' and distinguishes from sibling spectra_scan_opportunities by explaining difference in ranking methodology.

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 tells when to use (to find best fixed yields), and provides guidance on when to use this vs. spectra_scan_opportunities, with clear explanation of the intentional disagreement in rankings.

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