Skip to main content
Glama

BRAINIAC DeFi Intelligence

Get current protocol TVL

defi-intelligence_protocols_tvl_current

Retrieve current Total Value Locked (TVL) for a specific DeFi protocol from DeFiLlama public API. TVL is a delayed reference value. Price $0.01 USDC. POST /api/v1/defi-intelligence/protocols/tvl/current. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "defi-intelligence_protocols_tvl_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that TVL is a delayed reference value, the per-call price ($0.01 USDC), the POST endpoint, and that unpaid calls return 402 without executing. It omits response shape, pagination/limits, and rate-limit or auth details beyond payment.

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?

Four short sentences: purpose first, then data-quality caveat, then cost, then endpoint and failure mode. Nothing is redundant and the most decision-relevant facts (what it returns, that it costs money) are front-loaded.

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 simple one-parameter read tool with no annotations and no output schema, the description covers source, cost, data freshness, endpoint, and payment-failure behavior. The remaining shortfall is the identifier format and a hint at the returned payload, which the absent output schema leaves entirely undocumented.

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

Parameters2/5

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

Schema description coverage is 0% for the sole required parameter 'id', and the description does not clarify whether it is a DeFiLlama slug, a protocol name, or a chain-qualified identifier, nor any format constraints. For a single required identifier whose correct format determines success, this is a meaningful gap.

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?

States a specific verb and resource ('Retrieve current Total Value Locked (TVL) for a specific DeFi protocol') and names the data source (DeFiLlama public API). The phrase 'for a specific DeFi protocol' plus the endpoint path distinguishes it from defi-intelligence_chains_tvl (chain-level TVL) and from the profile/search siblings.

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?

Usage is implied by the singular-protocol framing and the single required parameter, but the description never states prerequisites or alternatives. In particular it doesn't tell the agent to resolve a protocol id via defi-intelligence_protocols_search first, nor when to prefer chains_tvl for aggregate data.

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