Skip to main content
Glama

DeFi Funding Arbitrage, Pendle & Prediction Odds MCP

Get Institutional Stablecoin Base Yields

get_institutional_stable_yields
Read-onlyIdempotent

Returns verified $10M+ TVL DefiLlama stablecoin pools separating sustainable base fee APY from emission incentives.

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": "get_institutional_stable_yields"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of top pools to return (default 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds useful provenance and composition detail (DefiLlama as source, a $10M+ verification filter, and the base-fee vs emission breakdown of returned yields), but it does not explain what 'verified' actually means, how fresh the data is, or how it is cached or refreshed.

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?

A single front-loaded sentence that earns its words and puts the retrieval action and scope first. It is slightly over-compressed, though: 'verified' and 'stablecoin pools separating sustainable base fee APY from emission incentives' read as dense jargon rather than plain statement of the return shape.

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?

For a one-optional-parameter read tool with annotations and no output schema, most of what an agent needs is present: source, universe, size floor, and the conceptual return composition. The gaps are the ordering rule behind 'top pools' and the freshness/refresh characteristics of the underlying DefiLlama data.

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?

Only one optional parameter with 100% schema coverage, so the schema carries the meaning and a 3 baseline applies. The description adds nothing about the limit beyond what the schema says, and notably leaves the ranking basis for 'top pools' undefined, which is the one parameter detail an agent would want.

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?

States a specific verb plus a precisely scoped resource: 'verified $10M+ TVL DefiLlama stablecoin pools' that separate 'sustainable base fee APY from emission incentives'. The universe, size filter, and data source are all named, and the domain is unmistakably distinct from the sibling tools (kimchi premium, Pendle, bridge quotes, funding spreads, prediction odds).

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?

Usage is only implied: 'institutional' plus the TVL floor and the base-vs-emission split suggest this is for evaluating durable yield rather than chasing incentive APR. There is no explicit when-to-use statement, no when-not-to-use condition, and no named alternative among the siblings.

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.