Skip to main content
Glama
yg-base-mcp
by ufo1898

yields

Fetches live Base stablecoin lending rates from Aave, Moonwell, and Compound III for on-chain comparison, with per-call USDC settlement via x402 and no signup.

Instructions

Base 稳定币最优收益(Aave / Moonwell / Compound III 实时链上利率) — 0.002 USDC per call (x402, Base USDC, no signup)

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

Input Schema

NameRequiredDescriptionDefault
_paymentNobase64 PAYMENT-SIGNATURE from a previous 402 challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the paid x402 model, Base USDC currency, no signup requirement, and the real-time on-chain data sources, but it omits read-only confirmation, rate limits, freshness guarantees, failure behavior, and return semantics.

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?

The definition is a single compact sentence with the resource and protocols front-loaded and pricing details in parentheses. It contains no filler, though it is dense and mixes data description with payment mechanics.

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 simple one-parameter tool with no annotations and no output schema, the description conveys the data sources, real-time nature, and cost. However, it leaves important gaps: it does not define what 'best yield' means (APY vs APR, reward inclusion), describe the output shape, or state freshness and rate-limit behavior.

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?

The schema fully documents the single optional _payment parameter, so the baseline is 3. The description adds real value beyond the schema by explaining that calls cost 0.002 USDC via x402 on Base USDC with no signup, which clarifies why a payment signature is needed, though it still does not explain the 402 challenge flow.

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 names the resource clearly: Base stablecoin best yield, with the protocols (Aave / Moonwell / Compound III) and real-time on-chain rates. An agent can tell it returns live yield data, though it does not explicitly contrast itself with siblings like pools or free_sample; the paid per-call framing only implicitly separates it from free_sample.

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 only usage-related information is the price and payment method ('0.002 USDC per call, x402, Base USDC, no signup'). There is no explicit when-to-use, when-not-to-use, or named alternative such as free_sample or pools, so the agent must infer when the paid live-yield tool is appropriate.

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

Deploy Server

Other Tools