Skip to main content
Glama

Teardrop

by dev.teardrop.api
OverviewDiscussionsAdmin

Get Protocol Tvl

get_protocol_tvl
Read-only

Get Total Value Locked for one or many DeFi protocols from DeFiLlama: current USD TVL, 7/30-day change, fees and revenue when reported, per-chain breakdown, and optional daily historical series. Batch multiple protocols via protocols=[...] — batch responses return one compact economic summary per protocol; single-protocol calls add chain and historical detail. Supports 3,000+ protocols; use DeFiLlama slugs ('aave-v3', 'uniswap-v3'); common aliases are auto-corrected.

Use when: Use for protocol-level economic questions — size, growth, fees, or revenue of a specific protocol. For 2+ protocols always batch in one call rather than calling per-protocol. Pass include_historical=true with days when a trend is needed; without it the response is a current TVL scalar. For ecosystem-level chain comparisons use get_chain_metrics instead.

Limitations: Third-party DeFiLlama analytics, not on-chain truth. Upstream revenue failures surface as revenue_error_type and null economic fields are data gaps — never fabricate values for them.

Alternatives: get_chain_metrics, get_yield_rates, get_dex_volume

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / days / title
      Added value: +"Days"
    • addedInput schema / properties / include_historical / title
      Added value: +"Include Historical"
    • addedInput schema / properties / protocol / title
      Added value: +"Protocol"
    • addedInput schema / properties / protocols / title
      Added value: +"Protocols"
    • addedInput schema / title
      Added value: +"mcp_get_protocol_tvlArguments"
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that this is third-party DeFiLlama analytics rather than on-chain truth, explains that upstream revenue failures surface as revenue_error_type, and warns that null economic fields are data gaps to never fabricate. It also describes batch-versus-single response differences, adding substantial behavioral context.

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 description is well-structured and front-loaded: capability, usage guidance, limitations, alternatives. Every sentence carries useful information, and the use of short labeled sections makes the guidance easy to scan without wasted words.

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?

Given the absence of an output schema, the description sufficiently explains what the tool returns: current TVL, historical series, fees/revenue, per-chain breakdown, and batch versus single response shapes. It also covers protocol slug format, alias behavior, and data-quality caveats, so an agent has enough context to 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%, but the description goes further by explaining the protocols=[...] batch mode, the compact batch response versus detailed single-protocol response, the meaning of include_historical and days, and the auto-correction of common aliases. This materially helps an agent choose and populate parameters correctly.

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 opens with a specific action and resource: 'Get Total Value Locked for one or many DeFi protocols from DeFiLlama' and enumerates concrete outputs like current USD TVL, 7/30-day change, fees, revenue, and per-chain breakdown. It also distinguishes itself from siblings by framing the tool for 'protocol-level economic questions' rather than ecosystem-level chain comparisons.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use when' section explicitly states when to use this tool, when to batch, when to set include_historical=true, and when to choose get_chain_metrics instead. The 'Alternatives' line further reinforces routing by naming related sibling tools.

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
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