Skip to main content
Glama

AutoTasker Hub — China Social Data API

defillama_chains

Top blockchain protocols by TVL from DeFiLlama. Market overview. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add one genuinely useful, non-schema fact: the call costs $0.01 USDC, which matters for an agent's budget decisions. Beyond that it says nothing about how many results come back, ordering beyond 'top', caching, or freshness.

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

Conciseness3/5

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

Three fragments, no waste, but the terseness borders on cryptic — 'Market overview' and the price tag are dropped in without connective context. It is compact rather than well-structured, and front-loading the paid aspect would have been clearer.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should explain what the response looks like (fields per chain, ordering, whether TVL is in USD) and what limit controls. It does neither, so an agent cannot predict output shape or cardinality before calling.

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?

There is one parameter (limit, default 10, max 50) with 0% schema description coverage, and the description never mentions it. The word 'Top' implies a ranked, limited result set but neither the ranking basis nor the meaning of limit is clarified, leaving the schema to speak for itself with no descriptive help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb-less noun phrase: 'Top blockchain protocols by TVL from DeFiLlama.' It identifies the resource and the sort metric, but calls the output 'protocols' while the tool name is defillama_chains, leaving genuine ambiguity about whether the result is a list of chains or of protocols. No sibling differentiation is offered.

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?

'Market overview' gestures at a use case but gives no explicit when-to-use, when-not-to-use, or alternative among the many sibling tools (e.g. chain_stats, defillama_pools). An agent must guess whether this or a sibling is the right entry point for TVL data.

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.