Skip to main content
Glama

AutoTasker Hub — China Social Data API

defillama_pools

Yield/farming pool data: APY, TVL, IL risk. For DeFi analysts. $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_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With annotations absent, the description carries the full burden and only discloses the price ($0.01 USDC) and the data fields. It says nothing about whether results are paginated, how pools are ordered or filtered by chain/protocol, how fresh the APY numbers are, or what triggers the charge — all material for a metered data endpoint.

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?

Very short and front-loaded, but written in telegraphic fragments where the audience tag adds little and the price is buried at the end. Nothing is wasted, yet the brevity comes at the cost of substance rather than serving it.

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 paid, paginated data tool with no annotations, no output schema, and 0% parameter coverage, the definition is materially under-specified. An agent cannot tell what it receives per pool, how many results a page holds, or how the USDC charge is settled.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters (page, limit) that have defaults and a maximum of 20. The description adds no meaning whatsoever for either — no ordering semantics, no statement of what a page contains or what happens past the limit.

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?

Names the resource precisely (yield/farming pools) and enumerates the data returned (APY, TVL, IL risk), which tells an agent exactly what domain of data to expect. It does not distinguish itself from siblings, but no sibling in the supplied list overlaps on pools, so the purpose is still decidable.

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 signal is the audience tag 'For DeFi analysts', which describes who, not when. There is no when-to-use, when-not-to-use, or alternative named, so an agent must infer selection from the topic alone.

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.