Skip to main content
Glama

Stratalize Intelligence

Get Chain Tvl Benchmark

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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: live data sourced from DeFiLlama and a per-call cost of $0.02 USDC, which matters for an agent managing spend. It does not describe result freshness guarantees, pagination, or error behavior, so it stops at adequate.

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?

Front-loaded with purpose and coverage, then the metric list, then cost — a sensible order with no wasted clauses. The metric enumeration earns its place because there is no output schema. The 'for x402 agent context' fragment is vague filler but small.

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?

With no output schema, listing returned metrics (rankings, 1D/7D change, protocol counts, ETH dominance, Base vs ETH comparison) usefully fills the return-value gap, and pricing/data source are disclosed. However, for a two-parameter tool with zero schema documentation, the absence of any parameter explanation leaves a real hole.

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 and largely does not. It never mentions 'limit' (range 1-50, presumably result count) and only hints at 'sort_by' via the words 'Rankings' and '1D and 7D change', without mapping those to the tvl/change_1d/change_7d enum values or stating a default.

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 and verb scope: live TVL by blockchain, naming covered chains (Ethereum, Base, Solana, Arbitrum, 50+ chains) and the data source (DeFiLlama). An agent can distinguish this from sibling benchmarks like get_defi_yield_benchmark or get_crypto_correlation_benchmark on domain alone, though no sibling is named.

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?

No when-to-use or when-not-to-use guidance. The phrase 'for x402 agent context' is unclear and does not tell the agent under what conditions this tool beats an alternative. Only implicit usage signal is the domain (chain-level TVL).

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