Skip to main content
Glama

Yield rates

yield_rates
Read-only

Get current DeFi yield rates (APY) across Solana protocols. Returns top pools sorted by TVL from Marinade, Jito, Raydium, Orca, and more via DeFiLlama. Costs $0.002 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yield_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain to query yields for (default: Solana)Solana

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context beyond annotations by disclosing the per-call cost ($0.002 USDC), data sources (Marinade, Jito, Raydium, Orca via DeFiLlama), and that results are sorted by TVL.

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 sentences with no wasted words. The core purpose and scope are front-loaded, and the cost and data-source details earn their place by informing invocation decisions.

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?

For a simple read-only tool with one optional parameter and no output schema, the description gives enough context to invoke correctly: what it returns ('top pools sorted by TVL'), APY focus, data sources, and cost. Minor gaps remain around output fields and pagination, but they are not critical for this 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 description coverage is 100% for the single chain parameter, so the schema already documents its meaning and default. The description does not add syntax, allowed values, or further semantics for the chain parameter, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Get current DeFi yield rates (APY) across Solana protocols.' It names specific protocols and data sources, which helps distinguish it from generic price tools. However, it does not explicitly differentiate from overlapping siblings such as lst_yields or lending_rates, which also cover DeFi yield data.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance or explicit alternatives. In a crowded sibling set containing l2_yield_scanner, lst_yields, and lending_rates, the agent is left to infer whether yield_rates is the right tool for a given yield query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources