Skip to main content
Glama

Dex volumes

dex_volumes
Read-onlyIdempotent

Live DEX trading volume across blockchains and decentralized exchanges (24h/7d/30d USD, change %, market share) via DefiLlama. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOptional sort: 24h (default), 7d, 30d, or change_1d.
chainNoOptional chain filter (e.g. Base, Solana, Ethereum, Arbitrum, BSC, Polygon).
limitNoOptional max protocols to return (1-50, default 20).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
protocolNoOptional protocol name filter (e.g. uniswap, aerodrome).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety basics are covered. The description adds materially new behavior: a $0.002 per-call charge, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the required two-step negotiation — none of which appears in the annotations or schema. It does not describe failure modes if payment is rejected or malformed.

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?

Two sentences, front-loaded with what the tool returns, then the payment mechanics. Every clause carries information an agent needs — metrics, price, rails, and the call-twice protocol — with no 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 five-parameter, all-optional, fully documented read tool with no output schema, the description covers what data comes back and how the paid handshake works. The remaining gap is response shape and payment-error behavior, which an agent must discover at runtime, but that is minor for a read-only listing endpoint.

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 sort values, chain examples, limit bounds (1-50, default 20) and protocol filtering are already fully documented in the schema. The description only echoes the 24h/7d/30d notion that maps to `sort` and otherwise adds no new parameter meaning; baseline 3 applies.

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?

The description states a specific resource and metric set: live DEX trading volume with 24h/7d/30d USD, change %, and market share, sourced from DefiLlama. That is enough to distinguish it in spirit from a new-pools tool, but it never names a sibling or explicitly scope-boundaries itself against one.

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 a concrete procedural rule for the paid endpoint: call once without `payment` to receive terms, then call again with `payment`. It does not say when to prefer this over related tools or when the data would be unsuitable (e.g. per-pool vs aggregate volume), so it stops short of full when/when-not guidance.

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