Skip to main content
Glama

Total value locked by chain from DefiLlama, largest first

defi_chains
Read-only

Total value locked by chain from DefiLlama, largest first, with each chain's token, chain id and stablecoin market cap. With chain, that chain's own row and its TVL change over 1, 7 and 30 days from DefiLlama's daily history. Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_tvl when you need total value locked in DeFi from DefiLlama; 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_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional chain name as DefiLlama spells it, e.g. Ethereum, Arbitrum, Base, Solana
limitNoChains to list, 1 to 50, default 20

Output Schema

NameRequiredDescriptionDefault
chainNo
countNo
chainsNo
sourceNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / chain
      Added value: +{}
    • removedOutput schema / properties / chainFilter
      Removed value: -{}
    • addedOutput schema / properties / chains
      Added value: +{}
    • removedOutput schema / properties / chainsCount
      Removed value: -{}
    • addedOutput schema / properties / count
      Added value: +{}
    • removedOutput schema / properties / topChains
      Removed value: -{}
    • removedOutput schema / properties / topProtocolsOnChain
      Removed value: -{}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark the tool read-only and open-world, and the description adds useful behavior beyond them: returned fields such as token, chain id, stablecoin market cap, and 1/7/30-day TVL changes when chain is supplied. It also discloses the x402 payment model, price per successful call, and that failed calls are not charged.

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 purpose and ordering are front-loaded, followed by parameter behavior, sibling alternatives, and pricing. It is dense but useful, with only minor repetition around DefiLlama as the data source and a slightly padded disclaimer.

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 output schema, the description need not explain return shapes exhaustively. It covers the key data source, ordering, optional chain behavior, sibling alternatives, and payment model, leaving little an agent needs before invoking it.

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 both parameters are already documented in the input schema. The description still adds meaning by explaining the special behavior of the chain parameter, including the row and historical TVL changes returned when it is provided.

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 states a specific resource and ordering: total value locked by chain from DefiLlama, largest first. It also distinguishes itself from siblings by naming defi_tvl for aggregate DeFi TVL and defi_stablecoins for stablecoin listings, so an agent can route correctly without opening schemas.

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?

It explicitly explains when to use this tool and names alternatives for different needs: defi_tvl for total DeFi TVL and defi_stablecoins for stablecoin supply and peg data. It also clarifies that supplying the optional chain parameter returns that chain's row and historical TVL changes.

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