Skip to main content
Glama

BRAINIAC DeFi Intelligence

Get TVL by blockchain

defi-intelligence_chains_tvl

Retrieve Total Value Locked (TVL) across blockchains from DeFiLlama public API v2. TVL is a delayed reference value. Price $0.03 USDC. POST /api/v1/defi-intelligence/chains/tvl. Unpaid calls return 402 and do not run.

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

Input Schema

NameRequiredDescriptionDefault
chainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description does add real behavioral context: the tool is a paid call ($0.03 USDC) that returns HTTP 402 and does not execute when unpaid, and TVL is a delayed reference value. What it omits is whether the call is read-only (implied by 'Retrieve' and POST), whether the chain filter is optional and what happens when it is omitted, and what the payload looks like.

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?

Four short sentences with the purpose front-loaded, followed by the data-freshness caveat and the payment mechanics. The endpoint path is arguably boilerplate, but nothing is verbose or buried.

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

Completeness3/5

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

For a one-parameter read tool with no annotations and no output schema, the description covers cost, failure mode, and data staleness, which is solid. It still leaves the agent guessing about the chain identifier format, the unfiltered default, and the shape of the returned TVL data, which the absent output schema cannot fill in.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional 'chain' parameter, so the description should carry the meaning and does not. 'Across blockchains' hints that omitting chain returns all chains, but the accepted identifier format (slug vs. display name vs. chain ID) and case sensitivity are never stated.

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?

The description names a specific verb and resource: 'Retrieve Total Value Locked (TVL) across blockchains' from DeFiLlama. The 'chains' scope implicitly separates it from the protocols_tvl_current sibling, but that distinction is never stated, so an agent must infer it from the name alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., use protocols_tvl_current for per-protocol TVL). The only guidance-like content is the payment/402 note, which governs invocation mechanics rather than tool selection.

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