A.U.G.U.R Synapse · Chain

DEX volume rankings

dex_volumes

Read-onlyIdempotent

DEX trading volume in the last 24 h / 7 d / 30 d — all chains or one — with the top DEXes and their share and change. DefiLlama DEX overview. Optionally scoped to one chain. Includes perps with type=perps (derivatives volume) or aggregators. Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).

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

Name	Required	Description	Default
`type`	No	Spot DEXes, perp/derivatives DEXes, or DEX aggregators. One of "dexs", "derivatives", "aggregators". Default "dexs".	dexs
`chain`	No	e.g. Solana, Base (optional)
`limit`	No	How many venues to return. Range 1-50. Default 15.

Output Schema

Name	Required	Description	Default
`top`	No
`type`	No
`scope`	No
`source`	No
`volume_usd`	No
`change_1d_pct`	No
`change_7d_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, idempotent=true, destructive=false, openWorld=true), so the description's added detail is what counts: 'Price: free' and the error contract ('returns isError with a message for invalid input or an upstream failure (not charged)') are genuinely useful operational facts not present in the annotations.

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?

Front-loaded with the core output (volume + top venues) and packed into a few dense sentences with no filler. Slightly overloaded with parenthetical clauses, but nothing is truly wasted.

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 zero-required-param read tool with a full output schema, the description covers scope, modes, chain scoping, pricing, and failure behavior. An agent has enough to call it correctly; only explicit sibling routing 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 each parameter is already documented with defaults and ranges, so the baseline is 3. The description's mapping of perps/aggregators is helpful, but it says 'type=perps' while the schema enum only accepts 'derivatives', which could lead an agent to submit an invalid value — a small but real mismatch.

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 names a specific verb+resource (DEX trading volume over 24h/7d/30d), the entity set (top DEXes with share and change), and the data source (DefiLlama DEX overview) plus chain scoping and perps/aggregator coverage. It is clearly a rankings tool, though it does not explicitly route against close siblings like cex_ticker, defi_rankings, or fees_revenue.

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 implied rather than stated: 'all chains or one', 'Optionally scoped to one chain', and the perps/aggregator variants hint at use cases but give no explicit when-to-use/when-not or alternative-selection guidance (e.g., DEX volume vs CEX volume vs protocol fees). Adequate but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All A.U.G.U.R Synapse · Chain tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?