Skip to main content
Glama

Defillama

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Defi Protocol Fees

defi_protocol_fees
Read-onlyIdempotent

Check daily fees and revenue for a DeFi protocol. Returns fee trends to analyze profitability and income changes over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
protocolYesProtocol slug (e.g., "aave", "uniswap", "lido")
data_typeNoType of data: "dailyFees" or "dailyRevenue" (default: "dailyFees")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProtocol name
protocolYesProtocol slug
total_7dNoTotal fees/revenue last 7 days in USD
data_typeYesType of fee data returned
total_24hNoTotal fees/revenue in last 24 hours in USD
total_30dNoTotal fees/revenue last 30 days in USD
total_all_timeNoTotal fees/revenue all time in USD
total_48h_to_24hNoTotal fees/revenue 48h-24h ago in USD
daily_chart_last_30YesLast 30 days of daily data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "daily_chart_last_30": {
+      "description": "Last 30 days of daily data",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "ISO date (YYYY-MM-DD)",
+            "type": "string"
+          },
+          "value": {
+            "description": "Daily fees/revenue in USD",
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "data_type": {
+      "description": "Type of fee data returned",
+      "enum": [
+        "dailyFees",
+        "dailyRevenue"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "description": "Protocol name",
+      "type": "string"
+    },
+    "protocol": {
+      "description": "Protocol slug",
+      "type": "string"
+    },
+    "total_24h": {
+      "description": "Total fees/revenue in last 24 hours in USD",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_30d": {
+      "description": "Total fees/revenue last 30 days in USD",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_48h_to_24h": {
+      "description": "Total fees/revenue 48h-24h ago in USD",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_7d": {
+      "description": "Total fees/revenue last 7 days in USD",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_all_time": {
+      "description": "Total fees/revenue all time in USD",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "protocol",
+    "data_type",
+    "name",
+    "daily_chart_last_30"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "protocol": "uniswap"
+  },
+  {
+    "data_type": "dailyRevenue",
+    "protocol": "aave"
+  }
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that it returns fee trends for profitability analysis, which is useful behavioral context beyond 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?

Two succinct sentences, front-loaded with the core action ('Check daily fees and revenue'), with no unnecessary words.

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?

Given the tool's low complexity (2 parameters, rich output schema), the description is fully adequate. Annotations and schema cover the rest.

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 parameters are well-documented in the schema. The description repeats the purpose ('fees and revenue') but does not add new parameter-level details.

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 uses specific verbs ('Check daily fees and revenue') and a resource ('DeFi protocol'), clearly distinguishing it from sibling tools like defi_chain_tvl or defi_yields.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., defi_protocol_detail, defi_yields). The agent is left to infer context from the tool name alone.

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

All Defillama toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources