Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

defi_tvl

Read-onlyIdempotent

Fetches DeFi TVL by chain, stablecoin circulating supply, or yield pools from DefiLlama. Use it to compare chains, track stablecoin supply, or filter pools by project and chain.

Instructions

[Trading Data API] DefiLlama data: TVL by chain, stablecoin circulating supply, or yield pools.

Example: /v1/defi-tvl?view=chains

Use when you need DeFi TVL by chain, stablecoin supply or yield pools from DefiLlama. Not for the health or risk of one protocol (use protocol_health_score).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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

Input Schema

NameRequiredDescriptionDefault
viewNoOptional. chains (default), stablecoins, or yields.
chainNoOptional (yields view). Filter pools by chain, e.g. Ethereum.
limitNoOptional. Rows to return (default 20, max 100).
projectNoOptional (yields view). Filter pools by project, e.g. aave-v3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the payment model (x402 USDC on Base, or free with an API key) and, critically, that an unauthenticated call returns HTTP 402 with a decoded price quote rather than an error. That prevents an agent from misclassifying a normal paid response as a failure.

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?

Structure is strong: capability line, example, usage routing, then behavioral notes. The second sentence partly restates the first (repeating the three views), a small redundancy that keeps it short of perfect.

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

Completeness4/5

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

There is no output schema, so the description should ideally hint at the return shape (e.g. a ranked list of chains with TVL values), which it does not. Everything else an agent needs — scope, exclusions, cost/auth behavior — is present.

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

Parameters3/5

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

Schema description coverage is 100%, so view/chain/limit/project are already documented, including defaults and max. The description adds only an example query string (`?view=chains`), which is marginal beyond the schema; baseline 3 applies.

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?

First line names the source (DefiLlama) and the three concrete resources: TVL by chain, stablecoin circulating supply, yield pools. The example endpoint plus the explicit exclusion of protocol-level risk data makes it distinguishable from siblings like protocol_health_score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when you need DeFi TVL by chain, stablecoin supply or yield pools" states the selecting condition, and "Not for the health or risk of one protocol (use protocol_health_score)" names the alternative and the boundary. Both when-to-use and when-not-to-use are explicit.

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

Deploy Server

Other Tools