Skip to main content
Glama

Defi chains tvl

defi_chains_tvl
Read-onlyIdempotent

Live DefiLlama TVL rankings across blockchains. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
sortNotvl (default) or name
limitNo1-50 (default 20)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the baseline is set. The description adds genuinely useful operational context beyond them: a concrete price ($0.004 per call), the x402 protocol, and the accepted payment assets. It doesn't say what happens if payment is invalid or how the challenge terms expire, so it's helpful but incomplete.

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?

Three tight sentences with the resource and the payment procedure front-loaded; no filler. The payment clause is dense but each element is load-bearing.

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?

For a read-only rankings endpoint with full schema coverage, the description covers scope, cost, and the purchase flow. The main gap is the shape of the result (what a chain entry contains), which matters somewhat because no output schema exists, but the rankings nature makes it largely predictable.

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

Parameters3/5

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

Schema coverage is 100% and every parameter already carries its own description, so the schema does the heavy lifting. The description reinforces the payment workflow but adds no syntax or format detail for `sort` or `limit` beyond what the schema states.

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?

States a specific resource (DefiLlama TVL rankings) and scope (across blockchains), which implicitly separates it from the protocol-level sibling defi_protocol_tvl. It never names that sibling or any alternative explicitly, so differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

The description gives an explicit two-call procedure for payment (call once without `payment`, sign, call again with `payment`), which is real usage guidance. It offers no guidance on when to choose this over defi_protocol_tvl or defi_yields, nor any exclusion conditions.

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