Get DeFi protocol TVL data from DefiLlama. Returns top protocols sorted by Total Value Locked. Filter by chain, minimum TVL, or get a single protocol by slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Single protocol slug for detail (e.g. aave, uniswap, lido) | |
| chain | No | Filter by blockchain (ethereum, bsc, solana, arbitrum, etc.) | |
| limit | No | Number of results (default 20, max 100) | |
| min_tvl | No | Minimum TVL in USD |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description discloses basic behavior (sorting by TVL, filtering), but lacks details on rate limits, pagination, data freshness, authentication, or side effects. Adequate but insufficient for full transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose and key features. No redundant information; every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and 4 parameters, the description covers main functionality but omits output format, sorting direction, limit max, and error handling. Adequate for basic use but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description rephrases schema fields without adding significant new meaning beyond 'filter by chain, minimum TVL, or get a single protocol by slug.' Does not enhance parameter understanding beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it retrieves DeFi protocol TVL data from DefiLlama, returns top protocols sorted by TVL, and offers filtering by chain, minimum TVL, or single protocol by slug. This is specific and distinguishes from siblings (get_chain_tvl, get_yield_pools).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies usage for protocol-level TVL queries, but does not explicitly contrast with siblings or state when not to use. Clear context but lacks explicit exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.