Skip to main content
Glama

dex_volume

[$0.005 USDC per call via x402] DEX trading volume: total 24h/7d volume and change, and the top DEXs by 24h volume, optionally for one chain (DefiLlama).

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": "dex_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name as on DefiLlama, e.g. Ethereum, Base, Solana, Arbitrum (default all)
limitNo1-50 (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add genuinely useful behavior: a cost of $0.005 USDC per call via x402 and the upstream source (DefiLlama). It does not address freshness, error behavior, or output structure, so the disclosure is helpful but incomplete.

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 tight sentence with no wasted words, and the payload (what data is returned) is front-loaded after the price tag. The bracketed cost prefix is boilerplate but carries real decision value for the caller.

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 simple two-parameter read tool with full schema coverage and no output schema, the description covers source, cost, and the shape of the data returned. Only minor gaps remain, such as default ordering and whether the limit applies to the DEX ranking.

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%, so both parameters are already documented with examples and defaults. The description only reinforces that 'chain' optionally narrows to one chain and never explains what 'limit' governs (number of top DEXs), so it adds marginal meaning.

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 the resource (DEX trading volume) and exactly what is returned: total 24h/7d volume plus change, and the top DEXs by 24h volume, with an optional single-chain scope. That is specific enough to separate it from siblings such as token_pairs or yields without opening a schema.

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?

Usage is only implied: it is evident the tool is for market volume data, and 'optionally for one chain' hints at the chain filter, but there is no explicit when-to-use versus alternatives, and no statement about defaults or limits beyond what the schema covers.

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