Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Defi protocol tvl

defi_protocol_tvl
Read-onlyIdempotent

Live DefiLlama TVL and per-chain breakdown for one or more DeFi protocols. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "protocol": "<protocol>"
    },
    "name": "defi_protocol_tvl"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
protocolYesprotocol slug or search, e.g. aave-v3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely new behavior: a $0.004 per-call price over x402, the accepted tokens and chains (USDC on Arc/Base/Solana, XNT on X1), and the mandatory two-call terms-then-payment sequence. That is exactly the kind of precondition an agent cannot infer from annotations.

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?

Three short sentences with zero filler: capability first, price/rails second, call sequence third. The reader hits the most decision-relevant facts up front.

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?

With no output schema, the description still sketches the return (live TVL plus per-chain breakdown) and fully documents the paid-call lifecycle. Remaining gaps are minor: no mention of units/currency, response shape, or what happens when a slug matches multiple protocols despite the 'one or more' phrasing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully explains `payment` as a signed payload that completes the purchase inside the same call, plus a slug example for `protocol`. It slightly undercuts itself by saying 'one or more protocols' while the schema requires a single string `protocol`, leaving the cardinality ambiguous.

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 concrete verb+resource: 'Live DefiLlama TVL and per-chain breakdown for one or more DeFi protocols.' The output shape (TVL plus per-chain split) and data source are named, so an agent can tell this apart from chain-level or yield-oriented siblings without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit operational guidance for the payment handshake: call once without `payment` to get terms, sign, then call again with `payment`. It does not state when to prefer this over the defi_chains_tvl sibling or what to do on payment failure, so the routing guidance is clear but not exhaustive.

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.