Skip to main content
Glama

Fees on a chain

chain_fees
Read-only

Protocols ranked by the fees or revenue they earned on one chain on the latest completed day (USD), 50 per page. The chain is a slug from chains. fees ranks across all chains; fees_history gives one protocol's days. 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": {
      "chain": "<chain>"
    },
    "name": "chain_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 protocols per page.
chainYesThe chain's slug, as listed by chains.
sort_byNofees or revenue, earned on the chain.fees
sort_orderNodesc for the highest first, asc for the lowest.desc

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 the safety profile is covered. The description adds real context beyond that: the data window is the latest completed day only, values are USD, page size is fixed at 50, and the upstream source is AlphaGrowth. It stops short of stating total-result bounds or pagination exhaustion behavior.

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, each earning its place: the first states what is returned and the unit, the second handles parameter provenance and sibling routing, the third credits the source. The core capability is front-loaded with zero filler.

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 four-parameter read-only ranking tool with a fully documented schema and no output schema, the definition covers temporal scope, currency, page size, and data provenance. Only the shape of returned fields and any rate-limit/caching expectation are left implicit, which is acceptable given the annotations.

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 description coverage is 100%, so all four parameters are already documented in structured data, including the chain-slug convention and the 50-per-page sizing. The description's 'chain is a slug from chains' and '50 per page' mostly restate the schema rather than adding new meaning, so 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 and resource — protocols ranked by fees or revenue earned on one chain on the latest completed day in USD — and immediately scopes it against siblings: 'fees ranks across all chains; fees_history gives one protocol's days.' An agent can distinguish this from both 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 Guidelines5/5

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

It explicitly routes the agent: use this when scoping to a single chain, use fees for cross-chain rankings, use fees_history for a single protocol's time series, and pull the chain value from chains. Both the when-to-use and the named alternatives are present.

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