Skip to main content
Glama
ymylive
by ymylive

get_protocol_tvl

Retrieve a protocol's metadata, current TVL across chains, and a trimmed history of daily total liquidity USD. Use after listing protocols to analyze one protocol's TVL trend per chain.

Instructions

Get a single protocol's metadata, current TVL, and recent TVL history.

Use after list_protocols to drill into one protocol — e.g. "what is Aave's TVL on each chain?" or "show me Lido's last 90 days of TVL." The raw DefiLlama response is enormous (multi-year daily series for the overall protocol AND every chain it touches), so this tool trims each history series to the last history_days daily points and drops the per-token breakdown arrays (tokens, tokensInUsd).

Args: slug: Protocol slug from list_protocols (e.g. "aave-v3", "lido", "uniswap-v3"). NOT a CoinGecko coin ID. history_days: Number of trailing daily points to keep for each TVL series. Default 90; use a smaller value for compactness or a larger value (up to ~1500) for long-range analysis.

Returns: Protocol object with id, name, symbol, category, chains, chain, description, url, mcap, currentChainTvls (snapshot per chain), tvl (recent series of {date, totalLiquidityUSD}), and chainTvls (per-chain trimmed series).

Note: slug is validated against ^[a-z0-9][a-z0-9._-]{0,127}$.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
history_daysNo
Behavior5/5

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

No annotations provided, but description fully discloses behavioral traits: it trims each history series to history_days, drops per-token breakdown arrays, and validates slug against regex. Also notes the raw DefiLlama response is enormous, adding important context.

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?

Description is fairly long but well-structured with clear sections: purpose, usage, args, returns, note. Every sentence adds value; minimal fluff. Could be slightly more concise but effective.

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?

No output schema, but description covers return object structure in detail. Parameter details are comprehensive, usage context is clear, and validation note included. Fully adequate for a two-parameter tool.

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

Parameters5/5

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

Schema coverage is 0%, but description adds thorough meaning: explains slug format with examples and validation hint, and history_days includes default, purpose, and typical range. Goes far beyond schema names/types.

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?

The description clearly states the tool gets a single protocol's metadata, current TVL, and recent TVL history, with specific examples (Aave, Lido). It distinguishes from sibling tools like list_protocols by focusing on drilling into one protocol.

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?

Explicitly says to use after list_protocols, gives example queries, clarifies slug is not a CoinGecko ID, and warns about raw response size and trimming behavior. Provides clear context for when to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ymylive/coin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server