Teardrop

Get Dex Volume

get_dex_volume

Read-only

Compare decentralized exchange activity from DeFiLlama. Returns 24-hour, 7-day, and 30-day volume, period-over-period changes, and each protocol's share of reported global 24-hour DEX volume. Filter by protocol names or DeFiLlama slugs and rank by a 1-, 7-, or 30-day lookback window.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of DEX protocols to return.
`protocols`	No	Optional protocol names or DeFiLlama slugs, such as ['uniswap-v3', 'curve-dex']. When omitted, return the largest DEX protocols.
`lookback_days`	No	Window used to rank the returned protocols: 1, 7, or 30 days (nearest supported window is used).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`dexes`	Yes
`error`	No
`error_type`	No
`total_matching`	Yes
`total_available`	Yes
`volume_share_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed11 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / limit / title
```
Added value: +"Limit"
```
addedInput schema / properties / lookback_days / title
```
Added value: +"Lookback Days"
```
addedInput schema / properties / protocols / title
```
Added value: +"Protocols"
```

addedInput schema / title

Added value: +"mcp_get_dex_volumeArguments"

addedOutput schema / $defs

Added value: +{
+  "DexVolumeEntry": {
+    "properties": {
+      "category": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Category"
+      },
+      "chains": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Chains",
+        "type": "array"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Error"
+      },
+      "error_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Error Type"
+      },
+      "protocol": {
+        "title": "Protocol",
+        "type": "string"
+      },
+      "slug": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Slug"
+      },
+      "volume_24h_usd": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 24H Usd"
+      },
+      "volume_30d_change_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 30D Change Pct"
+      },
+      "volume_30d_usd": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 30D Usd"
+      },
+      "volume_7d_change_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 7D Change Pct"
+      },
+      "volume_7d_usd": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 7D Usd"
+      },
+      "volume_share_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume Share Pct"
+      }
+    },
+    "required": [
+      "protocol",
+      "slug",
+      "category",
+      "volume_24h_usd",
+      "volume_7d_usd",
+      "volume_30d_usd",
+      "volume_7d_change_pct",
+      "volume_30d_change_pct",
+      "volume_share_pct",
+      "chains"
+    ],
+    "title": "DexVolumeEntry",
+    "type": "object"
+  }
+}

addedOutput schema / properties / dexes / items / $ref
```
Added value: +"#/$defs/DexVolumeEntry"
```

removedOutput schema / properties / dexes / items / properties

Removed value: -{
-  "category": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Category"
-  },
-  "chains": {
-    "items": {
-      "type": "string"
-    },
-    "title": "Chains",
-    "type": "array"
-  },
-  "error": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Error"
-  },
-  "error_type": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Error Type"
-  },
-  "protocol": {
-    "title": "Protocol",
-    "type": "string"
-  },
-  "slug": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Slug"
-  },
-  "volume_24h_usd": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 24H Usd"
-  },
-  "volume_30d_change_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 30D Change Pct"
-  },
-  "volume_30d_usd": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 30D Usd"
-  },
-  "volume_7d_change_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 7D Change Pct"
-  },
-  "volume_7d_usd": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 7D Usd"
-  },
-  "volume_share_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume Share Pct"
-  }
-}

removedOutput schema / properties / dexes / items / required

Removed value: -[
-  "protocol",
-  "slug",
-  "category",
-  "volume_24h_usd",
-  "volume_7d_usd",
-  "volume_30d_usd",
-  "volume_7d_change_pct",
-  "volume_30d_change_pct",
-  "volume_share_pct",
-  "chains"
-]

removedOutput schema / properties / dexes / items / title
```
Removed value: -"DexVolumeEntry"
```
removedOutput schema / properties / dexes / items / type
```
Removed value: -"object"
```

AddedAug 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds meaningful behavioral detail: it lists the exact metrics returned (24h/7d/30d volume, period-over-period changes, share of global volume) and the source. It does not contradict the annotations or hide any obvious side effects beyond what a read-only tool implies.

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?

The description is two tight sentences: the first front-loads the primary purpose, and the second enumerates the key metrics and filtering/ranking options. Every phrase earns its place with no redundancy or filler.

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?

With a read-only annotation, a fully documented 3-parameter schema, and an output schema present, the description provides sufficient selection and invocation context. It names the data source, return metrics, filtering options, and ranking window, leaving no obvious gaps for an agent to misuse the tool.

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?

The input schema already provides 100% coverage of all three parameters with clear descriptions, so the description does not add significant meaning beyond the schema. It restates the filtering/ranking semantics, but the schema already documents limit, protocols, and lookback_days accurately, warranting the baseline score.

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 opens with a specific verb ('Compare') and resource ('decentralized exchange activity from DeFiLlama'), making the tool's purpose immediately clear. It also distinguishes itself from siblings like get_dex_quote and get_protocol_tvl by focusing on volume comparison metrics.

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?

The description clearly establishes when to use the tool (when comparing DEX activity from DeFiLlama) and how to tailor it via protocol filters and lookback windows. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of full exclusion guidance.

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

All Teardrop tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources

Need Help?