Skip to main content
Glama

A DeFi protocol's fees and revenue for 24 hours, 7 days

defi_fees
Read-only

A DeFi protocol's fees and revenue for 24 hours, 7 days and 30 days, with the change over the last day against the day before, and the chains it runs on. Attribution: Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_dex_volume when you need a DEX's trading volume for 24 hours, 7 days and 30 days; defi_chains when you need total value locked by chain from DefiLlama, largest first. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolYesDefiLlama protocol slug, e.g. aave or uniswap-v3

Output Schema

NameRequiredDescriptionDefault
feesNo
chainsNo
sourceNo
revenueNo
protocolNo
checkedAtNo
disclaimerNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the commercial model ($0.002 per successful call via x402 USDC on Base/Solana and 10+ networks) and that failed calls are not charged, which directly affects retry strategy. It also states the data source (DefiLlama) and a liability disclaimer, none of which are in structured fields.

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?

One front-loaded sentence delivers purpose, timeframes, and the day-over-day delta before any boilerplate, and the sibling routing follows in a scannable list. The attribution, disclaimer, and payment sentences are justified for a paid endpoint but are denser than they need to be.

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 an output schema present, return values needn't be described, and the description covers scope, alternatives, pricing, and data source for a one-parameter read tool. The only gap is failure behavior — nothing says what happens when the protocol slug is invalid or the payment is declined.

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 coverage is 100% and the single parameter already carries its own description with an example ('aave or uniswap-v3'), so the schema does the documentation work. The tool description adds no extra meaning about slug format, case sensitivity, or what happens on an unrecognized slug, so the baseline 3 applies.

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 names a specific verb+resource (a DeFi protocol's fees and revenue) and enumerates the exact time windows returned (24h/7d/30d), the day-over-day change, and the chains covered. It also explicitly separates itself from defi_dex_volume (DEX trading volume) and defi_chains (TVL by chain), so an agent can pick it without opening any 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?

It gives explicit routing to two siblings with the condition that selects each ('when you need a DEX's trading volume', 'when you need total value locked by chain'). It never states a when-not or a prerequisite for this tool itself (e.g. what to do if the slug is unknown), so it is strong but not fully closed-loop.

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