Skip to main content
Glama

get_chain_tvl_benchmark

Read-only

Live TVL by blockchain — Ethereum, Base, Solana, Arbitrum, and 50+ chains from DeFiLlama. Rankings, 1D and 7D change, protocol counts, Ethereum dominance, and Base vs ETH TVL comparison for x402 agent context. $0.02 USDC per call.

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": "get_chain_tvl_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sort_byNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely new behavior: the upstream source is DeFiLlama and each call costs $0.02 USDC. With no output schema, listing the returned metrics (rankings, change windows, protocol counts, dominance) also earns credit. It stops short of stating rate limits, freshness/caching, or failure modes.

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?

Two dense sentences with the resource and scope front-loaded and cost last; little waste. The chain list and metric list are long but each item conveys real coverage, though the 'x402 agent context' clause adds little.

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?

Since there is no output schema, the description does a reasonable job of enumerating what comes back and flags the per-call cost. However, for a tool with two parameters at 0% schema coverage, the missing limit/sort semantics leave a real gap an agent must guess around.

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%, so the description must carry parameter meaning, but it never mentions the 'limit' parameter or its 1-50 range. 'Rankings, 1D and 7D change' only implicitly gestures at the sort_by enum values, leaving both parameters effectively undocumented.

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?

States a specific verb and resource ('Live TVL by blockchain'), names the covered chains, and identifies the data source (DeFiLlama). The scope (rankings, 1D/7D change, protocol counts, dominance, Base vs ETH comparison) makes it clearly distinguishable from sibling benchmark tools like get_defi_yield_benchmark or get_crypto_correlation_benchmark.

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?

The only usage framing is the vague phrase 'for x402 agent context', which does not say when to pick this over other crypto benchmarks or when not to. There is no mention of prerequisites, freshness, or alternatives.

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