Skip to main content
Glama

Ellimist

DeFi yield vs T-bill

data_defi_yield_vs_tbill
Read-only

Use this to compare parking USDC on Aave V3 with a 3-month U.S. Treasury bill right now: Aave's supply APR and APY, the T-bill yield, and the spread in basis points, with both source dates. Data comparison, not advice; Aave carries smart-contract risk a T-bill does not. Price: $0.01 USDC per call via x402 (no account). Not charged if it fails.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the price ($0.01 USDC via x402), that no account is needed, that failures are not charged, that figures are live ('right now') with source dates, and that Aave carries smart-contract risk a T-bill does not. That is substantive behavioral context an agent cannot get from structured fields.

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?

Purpose and outputs are front-loaded in the first clause, followed by risk caveat and pricing in short, purposeful sentences. Slightly dense (pricing, caveat, and comparison in one tool definition), but every element earns its place.

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 names the returned fields and their provenance, and covers cost and risk. The only material gap is the unexplained chain parameter, which matters for reproducibility of the Aave figure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the chain parameter or explains how base vs ethereum affects which Aave deployment is read. The enum and default are visible in the schema, but the description does nothing to compensate for the coverage gap.

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 and both sides of the comparison (USDC on Aave V3 vs 3-month T-bill) and enumerates the outputs (supply APR/APY, T-bill yield, spread in bps, source dates). This separates it cleanly from siblings like data_defi_aave_rates and data_macro_treasury_curve, which surface only one side.

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 opening 'Use this to compare ... right now' gives a clear triggering condition, and 'Data comparison, not advice' sets scope. It stops short of naming when to prefer a sibling (e.g., for raw Aave rates alone) or any exclusions, so it is strong but not exhaustive.

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