Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

defi_yield_matrix

[$0.25] Rank cross-chain DeFi liquidity pools with TVL >= $5M by risk-adjusted real base APY, impermanent loss exposure, and strategic allocation advice.

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_yield_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain (e.g. 'base', 'ethereum', 'arbitrum', 'solana', or 'all')base
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does contribute two useful facts: the tool is paid ($0.25) and results are gated by a TVL >= $5M filter. However, it says nothing about the LLM-backed degraded-response path, caching/freshness of APY data, or rate/accuracy limits, so key behavior is left undisclosed.

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?

One sentence, zero filler, with the price tag front-loaded and the purpose immediately after. It is dense but readable; the bracketed cost notation is slightly cryptic but still conveys useful information cheaply.

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 cross-chain, LLM-backed ranking tool with no annotations and no output schema, the definition omits the response shape entirely (per-chain? per-pool? ranked list with scores?) and only hints at the degraded path via the schema, not the description. It is adequate to select the tool but thin for predicting what comes back.

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% for both parameters (chain with examples and 'all', timeout_ms with degraded-mode semantics), so the schema already does the work and the baseline is 3. The description adds no parameter-level meaning beyond what the schema documents.

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 uses a specific verb ('Rank') and a specific resource ('cross-chain DeFi liquidity pools'), plus concrete ranking criteria (risk-adjusted real base APY, impermanent loss exposure, allocation advice) and a hard TVL floor of $5M. This is enough to separate it from siblings like defi_arbitrage_radar or defi_intent_routing, though no sibling is named explicitly.

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: the TVL filter and ranking criteria suggest 'use this to find the best risk-adjusted pool yields', but there is no explicit when-to-use statement, no when-not-to-use, and no alternative tool named. An agent must infer the trigger condition from the ranking criteria alone.

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