Crypto, web, finance and app data tools

DeFi Protocol TVL

defi_protocols_tvl

DeFi protocols by total value locked (DefiLlama): look up one protocol (aave, uniswap, lido) or rank them by chain and category (Lending, Dexs, Liquid Staking, Bridge...) with TVL, 1d/7d change, market cap and chains. Use for DeFi research and protocol comparisons.

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

Input Schema

Name	Required	Description	Default
`chain`	No
`limit`	No
`category`	No
`protocol`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully discloses the upstream data source (DefiLlama) and the returned fields (TVL, 1d/7d change, market cap, chains). It does not say how ranking is sorted, whether results are truncated by `limit`, or what happens for an unknown protocol name.

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?

Front-loaded with the resource and metric, then the two operating modes, then the use case. Dense but not padded; a single sentence carries the schema-relevant detail.

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?

An output schema exists, so return values need not be explained, and the description still names the key metrics returned. For a 4-param, fully optional filter tool the main remaining gap is mode interaction (protocol vs. chain/category precedence) and default ranking 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?

Schema description coverage is 0%, so the description must compensate and largely does: it explains `protocol` with concrete examples (aave, uniswap, lido), `chain`, and `category` with real category values even though the schema declares no enums. Only `limit` (default 25) is left unaddressed, keeping it short of a 5.

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?

States a specific resource (DeFi protocols), a specific metric (TVL), the data source (DefiLlama), and the two modes (single-protocol lookup vs. ranked listing). That clearly separates it from siblings like chains_tvl or protocol_fees, though it never names an alternative tool 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?

"Use for DeFi research and protocol comparisons" gives a use case, and the two modes with example values (aave, uniswap, lido) and categories (Lending, Dexs, Liquid Staking, Bridge) imply how to call it. But there is no guidance on when to pick this over chains_tvl, protocol_fees, or defi_yields, and no note on what happens if protocol and chain are combined.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?