Skip to main content
Glama

Teardrop

by dev.teardrop.api

Get Protocol Tvl

get_protocol_tvl
Read-only

Get Total Value Locked (TVL) data for a DeFi protocol from DeFiLlama. Returns current TVL in USD, 7-day and 30-day percentage change, and a per-chain breakdown. Set include_historical=True to also retrieve a daily TVL series for trend analysis. When DeFiLlama reports them, also returns current fees and revenue in USD with 7-day and 30-day percentage change. You can also batch multiple protocols via protocols=[...]. Supports 3,000+ protocols including Aave, Uniswap, Curve, Compound, Lido, MakerDAO, and more. Batch responses retain one compact economic summary per requested protocol; single-protocol calls include chain and historical detail. A revenue_error_type identifies an upstream revenue lookup failure. Use the DeFiLlama slug format: 'aave-v3', 'uniswap-v3', 'curve-dex'. Common aliases such as 'spark-protocol' and 'compound' are auto-corrected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days for the historical series (only used when include_historical=True).
protocolNoDeFiLlama protocol slug (e.g. 'aave-v3', 'uniswap-v3', 'curve-dex'). Use lowercase with hyphens as shown on DeFiLlama. Tip: 'aave' works for the combined Aave TVL; 'aave-v3' for V3 only. Optional when using batch mode via protocols=[...].
protocolsNoOptional batch mode: list of DeFiLlama protocol slugs. When provided, the tool returns one TVL result object per protocol.
include_historicalNoIf true, return a daily historical TVL series for the requested window.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true; description does not contradict. Adds beyond annotations by describing batch vs single-protocol response differences (compact summary vs detailed chain/history), revenue_error_type, and that historical series is optional. No mention of rate limits or auth, but readonly annotation covers safety.

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?

Description is 4-5 sentences, front-loaded with purpose and key outputs. Each sentence adds value (supported protocols, batch behavior, error type). Could be slightly tightened but no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 optional params, no output schema, and moderate complexity, the description covers return values, batch vs single differences, historical option, fees/revenue when available, and error identifier. Provides comprehensive context for an AI agent to select and invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 100% (4 params all described in schema). Description adds significant context: explains slug format with examples, distinguishes 'aave' vs 'aave-v3', clarifies days usage only when include_historical=True, and describes batch mode behavior. Greatly exceeds baseline.

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?

The description clearly states the tool gets TVL data for DeFi protocols from DeFiLlama, specifying returned metrics (current TVL, 7/30-day change, chain breakdown, optional historical, fees/revenue). It differentiates from sibling tools like get_dex_volume or get_lending_rates by being protocol-level TVL specific.

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?

Provides explicit usage guidance: slug format, batch mode via protocols=[...], auto-correction of aliases, and context for when to use single vs batch. Lacks explicit when-not-to-use or comparisons to alternatives, but purpose is narrow enough that it's clear.

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

All Teardrop toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct blockchain/DeFi resources and actions. A few pairs like get_lending_rates vs get_yield_rates and get_defi_positions vs get_liquidation_risk have overlapping boundaries, but detailed descriptions and explicit redundancy notes (e.g., get_eth_balance vs get_wallet_portfolio) reduce confusion.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., get_block, convert_currency, decode_transaction). The only minor deviations are noun-first names like http_fetch and web_search, but the style is uniform and predictable.

Tool Count2/5

At 27 tools, the server exceeds the 25-tool threshold for 'too many' and feels heavy. While the breadth of DeFi and crypto features justifies some size, the number is unwieldy for an agent to scan efficiently and could be consolidated (e.g., merging balance-related tools).

Completeness4/5

The tool surface covers a wide range of blockchain data: balances, prices, TVL, yields, DEX quotes, gas, block/transaction details, approvals, and DeFi positions. Gaps include lack of wallet transaction history and NFT support, but these are beyond the server's clear focus on read-only DeFi analytics.

Resources