Skip to main content
Glama

DEX, options and aggregator volumes

volumes
Read-only

Protocols ranked by trading volume, updated daily: kind dexs (spot DEX volume), options (options notional) or aggregators (DEX aggregator volume). Per protocol the 24h, 7d, 30d and 1y volume, the 1d/7d/30d change, its chains and category, with totals over the selection, 50 per page. With chain, each protocol's volume on that chain is chain_volume_24h_usd and the ranking and 24h total are that chain's (no 7d or 30d total). Free data from AlphaGrowth (alphagrowth.io).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNodexs, options or aggregators.dexs
pageNoPage number, 50 protocols per page.
chainNoA chain, by DefiLlama's chain key or name, case-insensitive (ethereum, base, arbitrum, bsc, solana, avax, hyperliquid).
sort_byNovolume_24h, volume_7d, volume_30d or change_1d.volume_24h
categoryNoA DefiLlama category, case-insensitive (Dexs, Derivatives, DEXAggregator, Options).
sort_orderNodesc for the highest first, asc for the lowest.desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description goes well beyond them: daily refresh cadence, 50-per-page pagination, totals computed over the selection, and a non-obvious quirk where the chain filter renames the metric to chain_volume_24h_usd and suppresses 7d/30d totals. That chain-mode caveat is exactly the kind of behavior an agent could not recover from the schema alone.

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?

A single dense paragraph that front-loads the resource and ranking behavior before the caveats. Every clause carries information, though the return-field enumeration makes it heavier than it needs to be; a short list of the chain-mode caveat would read faster.

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 compensates by naming the returned metrics (24h/7d/30d/1y volume, change fields, chains, category) and the aggregation behavior. Minor gaps remain: no guidance on invalid chain/category keys or what an empty result looks like, but nothing critical for correct invocation.

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 baseline is 3, but the description adds real meaning: it explains that the options kind is notional rather than premium volume and that aggregators means DEX aggregator volume, plus how `chain` changes the meaning of the returned ranking and totals. It does not elaborate on `sort_by` or `category` beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Protocols ranked by trading volume', and immediately scopes it with the three data kinds (spot DEX, options notional, DEX aggregator). It is clear what data domain the tool covers versus something like fee or TVL data, though it never names a sibling to differentiate against explicitly.

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

Usage Guidelines3/5

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

The description clarifies what each `kind` value means, which implicitly guides variant selection, but gives no when-to-use versus when-to-use-another-tool guidance and no exclusions. An agent must infer that this is the right tool for volume rankings rather than being routed to it.

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