Skip to main content
Glama

Total value locked in DeFi from DefiLlama

defi_tvl
Read-only

Total value locked in DeFi from DefiLlama. For a protocol (its slug, e.g. aave-v3) the current TVL; for a chain (Base, Ethereum...) its TVL with 1-day and 7-day changes. A protocol's history is too large to read here, so it has no change figures. Attribution: Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_chains when you need total value locked by chain from DefiLlama, largest first; defi_stablecoins when you need to list stablecoins with supply and peg from DefiLlama. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
chainNoOr a chain name, e.g. Base
protocolNoDefiLlama protocol slug, e.g. aave-v3

Output Schema

NameRequiredDescriptionDefault
noteNo
slugNo
typeNo
sourceNo
tvlUsdNo
checkedAtNo
disclaimerNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses cost and payment mechanics ($0.002 per successful call, x402 USDC on Base/Solana and 10 more networks, failed calls free), plus an attribution requirement and the limitation that protocol history is too large to return so no change figures appear. Those are exactly the operational facts annotations cannot carry.

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?

The core behavior is front-loaded in the first two sentences and the sibling routing follows logically. The closing pricing/attribution sentence is dense and slightly long, but each clause (price, payment rail, failed-call policy) carries decision-relevant information rather than filler.

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 an output schema present the description need not document return fields, and it correctly focuses on mode selection, limitations, cost, and siblings. The only meaningful omission is the no-argument default behavior, which matters given zero required parameters.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining what the two optional parameters select (protocol slug e.g. aave-v3 versus chain name e.g. Base) and what each variant returns. It does not say what happens when both or neither are supplied, which keeps it below a 5.

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 names a specific metric and source ("Total value locked in DeFi from DefiLlama") and then splits the two supported modes precisely: a protocol slug like aave-v3 returns current TVL, a chain like Base or Ethereum returns TVL with 1-day and 7-day changes. An agent can tell exactly what resource it reads and what shape of answer each argument produces.

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?

It explicitly routes to alternatives ("defi_chains when you need total value locked by chain... largest first; defi_stablecoins when you need to list stablecoins") and notes that protocol history is not available here. The one soft spot is that this tool still accepts a chain for a single-chain TVL, so the boundary against defi_chains is described but not fully disambiguated for that overlapping case.

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