Skip to main content
Glama

Fees and revenue history

fees_history
Read-only

A protocol's fees and revenue per day (USD) for up to 3650 days, with the period's totals and its fees on each chain on the latest day; chain_history=yes adds each chain's daily series. Version-split parents (Uniswap) carry no chain split: ask for a version (uniswap-v3). fees ranks protocols by the latest day. Free data from AlphaGrowth (alphagrowth.io).

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": {
      "slug": "<slug>"
    },
    "name": "fees_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of daily history, counting today.
slugYesThe project's slug; find it with find_projects or fees.
chain_historyNoyes to add each chain's daily series over the same days.no

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real context beyond them: data provenance ('Free data from AlphaGrowth'), the 3650-day ceiling, and the version-split caveat that affects which slug yields chain-level data. It does not discuss rate limits, freshness lag, or what 'latest day' means for revision, so it is not exhaustive.

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?

The return shape and constraints are front-loaded in the first clause, which is the right ordering. It is a single dense semicolon-chained sentence plus two short trailing notes, so it reads slightly packed, and the AlphaGrowth provenance note is the least load-bearing element, but nothing is truly wasted.

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?

There is no output schema, yet the description fully specifies what comes back: a daily USD series, period totals, and each chain's fees on the latest day, with optional per-chain daily series. Combined with the horizon cap and the version-split rule, an agent has everything needed to call it correctly and interpret the response.

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 description coverage is 100%, so a baseline of 3 applies, but the description adds meaning the schema lacks: the version-slug constraint for parents like Uniswap, the fact that `days` counts today and caps at 3650, and the effect of `chain_history` on the returned series. The `slug` pointer to find_projects or `fees` is a concrete discovery hint.

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 resource (a protocol's daily fees and revenue in USD), the return payload (daily series, period totals, per-chain latest-day fees, optional per-chain series), and the maximum horizon. It also distinguishes itself from the sibling `fees`, which 'ranks protocols by the latest day,' so an agent can pick between the ranking tool and the history tool without opening either 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 clear selection context: use `fees` for ranking, use this for daily history, set `chain_history=yes` to get per-chain series. It also carries a genuinely useful prerequisite-style warning that version-split parents like Uniswap carry no chain split and require a version slug (uniswap-v3). No explicit exclusions or alternatives beyond `fees` are stated, which keeps it short of a 5.

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