Skip to main content
Glama

Defillama

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Defi Chain Tvl

defi_chain_tvl
Read-onlyIdempotent

Compare total value locked across all blockchains. Returns TVL per chain to identify where capital is concentrated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainsYes
total_chainsYesTotal number of chains tracked

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chains": {
+      "items": {
+        "properties": {
+          "gecko_id": {
+            "description": "CoinGecko ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Blockchain name",
+            "type": "string"
+          },
+          "token_symbol": {
+            "description": "Native token symbol",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tvl": {
+            "description": "Total value locked in USD",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "tvl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_chains": {
+      "description": "Total number of chains tracked",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_chains",
+    "chains"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's additional context (returns TVL per chain, purpose) is useful but not critical. No contradictory statements. The description adds moderate value beyond annotations by clarifying output granularity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the core action ('Compare total value locked') and adding purpose ('to identify where capital is concentrated'). Every word earns its place; no fluff or repetition.

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 zero parameters and an output schema likely defining return values, the description is complete for this tool. It explains the tool's functionality and utility without requiring additional context.

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?

The tool has zero parameters, and schema description coverage is 100% (empty schema). Baseline score of 4 applies because no parameter documentation is needed. The description implicitly confirms no input is required, which matches the schema.

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?

Description clearly states the tool compares total value locked across all blockchains and returns TVL per chain to identify capital concentration. Verb 'compare' and resource 'total value locked across blockchains' are specific, and the tool is distinct from siblings like defi_protocol_detail (focuses on protocols) or defi_tvl_protocols (aggregates protocol-level TVL).

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 implies usage for comparing chain-level TVL and identifying capital concentration, but does not explicitly state when to use this tool versus alternatives (e.g., defi_protocol_detail for protocol-level data). No exclusions or prerequisites are mentioned, leaving some ambiguity for an AI agent choosing among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Defillama toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources