Skip to main content
Glama

Solana TVL

solana_tvl
Read-only

Solana ecosystem TVL analytics via DeFi Llama. Returns total TVL, top protocols ranked by TVL, category breakdown (DEX, Lending, Liquid Staking, etc.), 7-day trend, and Solana's market dominance as % of total DeFi. Filter by category for focused analysis. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTop protocols to return (default: 20)
categoryNoFilter by DeFi category (e.g. 'Dexes', 'Lending', 'Liquid Staking')
includeHistoryNoInclude 30-day daily TVL history (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world analytics call. The description adds useful behavioral context by naming the upstream source (DeFi Llama) and disclosing the $0.005 USDC per-call cost, though it does not discuss freshness, rate limits, or payment mechanics.

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

Conciseness5/5

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

The description is concise and front-loaded: it states the purpose first, then the returned data, then a filtering hint, then cost. Every sentence contributes useful information without unnecessary repetition.

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?

For a read-only analytics tool with three optional, fully documented parameters and no output schema, the description gives a strong overview of return values and cost. It could be slightly more complete by clarifying the relationship between the advertised 7-day trend and the includeHistory parameter, which exposes 30-day daily history.

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 the schema already documents all three parameters. The description adds only a general note about filtering by category and does not clarify limit or includeHistory semantics, so the baseline of 3 is appropriate.

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?

The description states a specific resource and scope: Solana ecosystem TVL analytics, with returned metrics enumerated. It is clearly distinguishable from the many adjacent crypto tools, but it does not explicitly name a sibling or contrast itself with alternatives.

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

Usage Guidelines3/5

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

The only usage hint is "Filter by category for focused analysis," which explains a parameter use case rather than when to choose this tool over alternatives. The intended context is implied by the name and description, but no exclusions or explicit alternatives are provided.

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.

Resources