Skip to main content
Glama

Vibe Springs

by net.vibesprings

get_defi_yields

Premium cross-protocol DeFi yield aggregator and scanner powered by DefiLlama. Scans Aave, Compound, Uniswap, Morpho, and 100+ protocols for the best APY opportunities across chains. Filter by token, chain, and minimum TVL. [PAID: $0.06 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by: apy, tvl, or protocolapy
chainNoFilter by chain: base, ethereum, arbitrum, optimism. Omit for all chains.
limitNoMax results
tokenNoFilter by token symbol (e.g. USDC, ETH, WBTC)USDC
min_tvlNoMinimum TVL in USD
payment_signatureNoOptional x402 payment token. Call the tool WITHOUT this first to receive payment requirements (price, payTo, asset, nonce rules), sign the exact-scheme EIP-712 USDC authorization with your wallet, then retry with this field set to the base64 token.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
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 paid nature ($0.06 per call via x402) and the two-step call requirement, which are critical behavioral traits. However, it omits failure modes, rate limits, or data update frequency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences plus a payment note. No redundant information. The main purpose is front-loaded, and the payment details are essential for correct invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description does not specify the output format or fields returned. It mentions 'best APY opportunities' but lacks details on error handling or pagination. For a paid tool, more completeness would be beneficial.

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 is 3. The description adds value by explaining the payment_signature parameter's two-step process in detail, which goes beyond the schema's description. It also reiterates the filter dimensions (token, chain, min_tvl).

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 this is a DeFi yield aggregator scanning 100+ protocols for best APY opportunities. It specifies the resource (DefiLlama-powered aggregator) and the action (scans and filters), distinguishing it from sibling tools like get_crypto_prices or get_gas_prices.

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 explains filtering by token, chain, and TVL, and notes the two-step payment process. While it doesn't explicitly state when not to use this tool, the context is clear and sufficient for selecting the tool among the unrelated siblings.

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

All Vibe Springs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_crypto_prices overlaps partially with get_market_pulse (which includes crypto prices), and get_exchange_rates overlaps with convert_currency. Descriptions clarify boundaries, but minor confusion possible.

Naming Consistency4/5

Nearly all tools follow a get_<noun> or verb_noun pattern, with consistent snake_case. The only outlier is 'health' which is a single word, but it still fits as a status endpoint.

Tool Count4/5

22 tools is slightly high for a single server, but each tool offers a distinct paid endpoint and the variety justifies the count. The server would benefit from a bit more focus, but it's still acceptable.

Completeness4/5

The server covers a wide range of data (crypto, weather, finance, on-chain risk, travel) with search and health endpoints. Missing operations like delete_watch or list_watches are minor gaps, but core functionality is well represented.

Resources