Skip to main content
Glama

LST yields

lst_yields
Read-only

Compare Solana Liquid Staking Token (LST) yields. Covers mSOL, jitoSOL, bSOL, INF, jupSOL, and 15+ LSTs across Marinade, Jito, Sanctum, BlazeStake, and more. Returns APY, TVL, best yields by TVL tier, and ecosystem average. Data from DeFi Llama. Costs $0.005 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": "lst_yields"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default: 20)
minTvlNoMinimum TVL in USD (default: 1,000,000)
sortByNoSort by: 'apy' or 'tvl' (default: apy)apy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior, but the description adds genuinely new operational context: the upstream data source (DeFi Llama) and an explicit per-call cost of $0.005 USDC. It also lists the returned fields, which tells the agent what a call yields beyond the safety profile.

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?

Three tight sentences: what it compares, what it covers, what it returns and costs. Scope is front-loaded and nothing is redundant with the name or title.

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?

With no output schema, the description usefully enumerates return fields (APY, TVL, best yields by TVL tier, ecosystem average) and discloses cost and data source. It stops short of noting freshness/cadence or how many LSTs a default call returns across the limit parameter, but is otherwise sufficient to invoke correctly.

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% with defaults on all three parameters (limit, minTvl, sortBy), so the description does not need to re-document them. It only gestures at the TVL-tier concept obliquely via 'best yields by TVL tier' and adds no format or unit detail beyond the schema, so baseline 3 applies.

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?

Specific verb plus resource: 'Compare Solana LST yields,' with the covered token universe (mSOL, jitoSOL, bSOL, INF, jupSOL, 15+ LSTs) and protocols (Marinade, Jito, Sanctum, BlazeStake) spelled out. This clearly separates it from the generic yield_rates and the chain-agnostic l2_yield_scanner siblings.

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

Usage Guidelines3/5

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

The Solana-LST scope implies when to reach for it, but there is no explicit when-to-use or when-not-to-use language and no sibling is named as an alternative. An agent must infer that yield_rates is the broader fallback rather than being told.

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