Skip to main content
Glama

DeFi yields vs T-bill spread (x402)

defi_vs_riskfree_spread

Read-onlyIdempotent

$0.01 via x402: top stablecoin DeFi yields vs official US T-bill rate — spreads + verdict (TradFi x DeFi in one 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": "defi_vs_riskfree_spread"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_tvlNoMinimum pool TVL USD, default 10000000
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, and open-world behavior. The description adds meaningful operational context: the call costs $0.01 via x402, which tells the agent this is a paid endpoint and that payment handling is part of invocation. It does not disclose data freshness, source details, or rate limits.

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?

The definition is a single compact sentence that front-loads the price and then the tool's purpose. It contains no filler and gives the essential differentiator immediately.

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 two-parameter, read-only comparison tool with no output schema, the description is largely complete: it says what is compared and that spreads plus a verdict are returned. The main remaining gap is source/freshness context for the yields and T-bill rate.

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 min_tvl and x_payment are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema; it only frames the overall comparison. With full schema coverage, the baseline of 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 clearly states a specific comparison: top stablecoin DeFi yields versus the official US T-bill rate, producing spreads and a verdict. It distinguishes itself from a generic DeFi-yields tool by emphasizing the TradFi-versus-DeFi spread and one-call verdict, though it does not explicitly name a sibling alternative.

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 comparison framing implies when the tool is useful: when an agent needs a DeFi-versus-risk-free-rate spread rather than raw yield data. However, there is no explicit when-to-use versus when-not guidance, and no direct routing to defi_yields or other alternatives.

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