Skip to main content
Glama

A DEX's trading volume for 24 hours, 7 days and 30 days

defi_dex_volume
Read-only

A DEX's trading volume for 24 hours, 7 days and 30 days, with the change over the last day and the chains it trades on. Attribution: Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_fees when you need a DeFi protocol's fees and revenue for 24 hours, 7 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_dex_volume"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
chainsNo
sourceNo
volumeNo
protocolNo
checkedAtNo
disclaimerNo
attributionNo

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 only declare readOnlyHint and openWorldHint, so the description usefully adds the pricing model ($0.002 per successful call via x402 in USDC, failed calls not charged) and the DefiLlama attribution and not-financial-advice framing. It doesn't cover latency or data freshness, but the cost and safety context it does add is materially useful for agent decisioning.

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 purpose is front-loaded in the first clause, and everything after is routing or cost context rather than padding. The legal and attribution clauses are boilerplate but short, and the whole thing stays within a compact block.

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?

For a one-param read tool with an output schema already describing return values, the description covers purpose, scope, cost, attribution, and the sibling alternatives an agent would otherwise have to guess between. Nothing needed to select or call it correctly is missing.

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 schema already documents the single required 'protocol' parameter with a concrete example slug (uniswap-v3). The description adds no further meaning about the param, 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 resource (a DEX's trading volume) with explicit scope (24h, 7d, 30d, day-over-day change, chains traded on), and it explicitly distinguishes itself from defi_fees and defi_chains by stating what each of those covers instead.

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: defi_fees for protocol fees and revenue, defi_chains for TVL by chain, largest first, leaving this tool as the one for DEX volume. The alternative and the condition that selects it are both stated, not left to inference.

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