Skip to main content
Glama

stablecoin-yield

by money.barker

barker_defi_vaults

Query real-time stablecoin supply yield pools from Barker's index of 500+ DeFi protocols. Returns ranked rows with protocol_name, chain_name, asset_symbol, supply_apy_total (decimal — multiply by 100 for %), and supply_tvl (USD). Use for questions like 'best stablecoin yield', 'where to earn on USDC', 'compare lending rates', '稳定币利率'. (paid: $0.001 per call via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort key
assetNoStablecoin symbol (lowercase): usdt, usdc, dai, usde, usds, fdusd, gho, crvusd, pyusd, sdai, frxusd, tusd, lusd, dola, etc.
chainNoChain name (lowercase): ethereum, bsc, arbitrum, base, polygon, optimism, avalanche, solana, etc.
limitNoRow count (default 50, max 100)

TDQS

A4.2/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 describes output fields, mentions real-time, and states the cost. It does not explicitly state read-only or error behavior, but the provided details are sufficient for a query tool.

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 sentences, front-loaded with purpose, then output, then examples. No fluff.

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?

Despite no output schema, the description explains return fields clearly. Parameters are fully covered in schema. Missing details like sorting default or pagination, but overall complete for a 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 description coverage is 100%, so baseline is 3. The description adds context about output fields (e.g., multiplying apy by 100) but does not add meaning to parameters beyond the 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?

The description clearly states the tool queries stablecoin supply yield pools from a specific index, using a strong verb 'Query' and specifying the resource. It distinguishes itself from siblings by focusing on stablecoins and yield pools.

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 provides explicit usage examples ('best stablecoin yield', 'where to earn on USDC') and implies the tool is for stablecoin yield questions. It does not explicitly exclude alternatives but the context is clear.

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

All stablecoin-yield 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

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: yield recommendation, pool listing, execution discovery, quoting, detail/history, market data, cross-chain routes, and position monitoring. No two tools overlap in functionality.

Naming Consistency5/5

All tools follow the consistent pattern 'barker_<domain>_<action>' using snake_case. The naming is descriptive and predictable, making it easy for an agent to understand the purpose of each tool.

Tool Count5/5

With 11 tools, the server covers the entire stablecoin yield workflow without being bloated. Each tool contributes to discovery, execution, monitoring, or market analysis, and none feel superfluous.

Completeness5/5

The tool set provides end-to-end coverage for stablecoin yield management: from discovery and analysis to execution and position monitoring. Missing features like batch position queries are outside the server's stated scope.

Resources