Teardrop

Get Dex Quote

get_dex_quote

Read-only

Get the best Uniswap v3 swap quote on Ethereum (chain_id=1) or Base (chain_id=8453) via direct on-chain QuoterV2 calls. Queries all four fee tiers (100/500/3000/10000 bps) in parallel and returns the tier with the highest output amount, along with per-tier breakdown. Inputs are raw uint256 amounts and EIP-55 checksummed addresses; native ETH is not quoted directly — pass the WETH address. Returns no_liquidity=true when no pool exists for the pair. Point-in-time quote at the returned block_number; do not cache.

Input Schema

TableJSON Schema

Name	Required	Description
`chain_id`	No	1 = Ethereum mainnet, 8453 = Base mainnet. Other chains unsupported.
`token_in`	Yes	EIP-55 checksummed address of the token being sold. For native ETH, pass the WETH address (Ethereum: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2; Base: 0x4200000000000000000000000000000000000006).
`amount_in`	Yes	Input amount in RAW uint256 units (e.g. '1000000' for 1 USDC, '1000000000000000000' for 1 WETH). Must be > 0 and < 2^128. Common token decimals: WETH/ETH/DAI/wstETH/cbETH/weETH 18, WBTC/cbBTC 8, USDC/USDT 6. Do not call read_contract to look up decimals — use these values directly.
`token_out`	Yes	EIP-55 checksummed address of the token being bought.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain_id`	Yes
`token_in`	Yes
`amount_in`	Yes
`token_out`	Yes
`amount_out`	Yes
`block_number`	Yes
`no_liquidity`	Yes
`fee_tier_used`	Yes
`effective_rate`	Yes
`quotes_per_tier`	Yes
`amount_out_human`	Yes
`amount_in_decimals`	Yes
`amount_out_decimals`	Yes

Schema Changelog

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

Changed12 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / amount_in / title
```
Added value: +"Amount In"
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```
addedInput schema / properties / token_in / title
```
Added value: +"Token In"
```
addedInput schema / properties / token_out / title
```
Added value: +"Token Out"
```

addedInput schema / title

Added value: +"mcp_get_dex_quoteArguments"

addedOutput schema / $defs

Added value: +{
+  "TierQuote": {
+    "properties": {
+      "amount_out": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Amount Out"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Error"
+      },
+      "fee_tier": {
+        "title": "Fee Tier",
+        "type": "integer"
+      },
+      "gas_estimate": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Gas Estimate"
+      },
+      "sqrt_price_x96_after": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Sqrt Price X96 After"
+      },
+      "success": {
+        "title": "Success",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "fee_tier",
+      "success"
+    ],
+    "title": "TierQuote",
+    "type": "object"
+  }
+}

addedOutput schema / properties / quotes_per_tier / items / $ref
```
Added value: +"#/$defs/TierQuote"
```

removedOutput schema / properties / quotes_per_tier / items / properties

Removed value: -{
-  "amount_out": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Amount Out"
-  },
-  "error": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Error"
-  },
-  "fee_tier": {
-    "title": "Fee Tier",
-    "type": "integer"
-  },
-  "gas_estimate": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Gas Estimate"
-  },
-  "sqrt_price_x96_after": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Sqrt Price X96 After"
-  },
-  "success": {
-    "title": "Success",
-    "type": "boolean"
-  }
-}

removedOutput schema / properties / quotes_per_tier / items / required
```
Removed value: -[
-  "fee_tier",
-  "success"
-]
```
removedOutput schema / properties / quotes_per_tier / items / title
```
Removed value: -"TierQuote"
```
removedOutput schema / properties / quotes_per_tier / items / type
```
Removed value: -"object"
```

First observedJul 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description enriches the readOnlyHint annotation with critical behavioral details: it queries four fee tiers in parallel, returns the best tier plus a breakdown, reports no_liquidity=true when no pool exists, and returns a block_number for point-in-time quotes. It also cautions against caching. This goes well beyond the annotation's safety signal.

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 a single, information-dense paragraph. Every sentence contributes unique value: purpose, mechanism, input formats, native ETH caveat, no-liquidity behavior, and point-in-time nature. There is no redundancy or fluff.

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?

Given the tool's complexity (multi-chain, four fee tiers, specific input constraints), the description covers all essentials: supported chains, parallel tier queries, output choice, no-liquidity handling, and freshness caveat. It even warns against caching. The presence of an output schema means return values need not be fully described, and the description is complete enough for an agent to use the tool correctly.

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 the schema already thoroughly documents token_in, token_out, amount_in, and chain_id. The description adds a brief note about raw uint256 amounts and EIP-55 addresses, but this largely duplicates schema content. Since the schema handles parameter explanations, the description adds minimal additional semantic value.

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 clearly states the tool's function: obtaining the best Uniswap v3 swap quote on Ethereum or Base. It specifies the method (direct on-chain QuoterV2), the resource (Uniswap v3), and the scope (chain_ids 1 and 8453). This distinguishes it from sibling tools like get_token_price or get_dex_volume.

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 provides clear context: it is for on-chain swap quotes, explicitly lists supported chains, and explains that native ETH is not quoted directly (use WETH). It also warns against caching due to point-in-time quotes. While it does not explicitly name alternative tools, the intended usage is unmistakable given the specific inputs and behavior.

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?