Quietwork Swap

debridge_quote

Cross-chain EVM swap quote via deBridge DLN (ethereum, base, arbitrum, optimism, polygon, bsc; e.g. USDC on Base -> ETH on Arbitrum). Includes the same disclosed 0.1% Quietwork affiliate fee PLUS deBridge's own fees (4 bps protocol fee, flat native-coin fee, ~4 bps solver margin, solver gas), all itemised.

Input Schema

Name	Required	Description
`amount`	Yes
`tokenIn`	Yes	symbol or 0x address on srcChain
`dstChain`	Yes
`srcChain`	Yes
`tokenOut`	Yes	symbol or 0x address on dstChain

Output Schema

Name	Required	Description
`fee`	Yes	Disclosed Quietwork fee (already reflected in expectedOut)
`venue`	Yes
`flatFee`	No
`tokenIn`	Yes
`amountIn`	Yes
`dstChain`	Yes
`srcChain`	Yes
`tokenOut`	Yes
`dstChainId`	Yes
`srcChainId`	Yes
`amountInUsd`	No
`amountInWei`	Yes
`expectedOut`	Yes
`amountOutUsd`	No
`deBridgeCosts`	Yes	deBridge's own fees, on top of ours
`expectedOutWei`	Yes
`flatFeeNativeWei`	No
`requestedAmountInWei`	No
`includesOperatingExpensesWei`	No
`approximateFulfillmentDelaySec`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "amountIn": {
+      "type": "string"
+    },
+    "amountInUsd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "amountInWei": {
+      "type": "string"
+    },
+    "amountOutUsd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "approximateFulfillmentDelaySec": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "deBridgeCosts": {
+      "description": "deBridge's own fees, on top of ours",
+      "properties": {
+        "flatFeeNativeWei": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "operatingExpenses": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "protocolFee": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "takerMargin": {
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "dstChain": {
+      "type": "string"
+    },
+    "dstChainId": {
+      "type": "integer"
+    },
+    "expectedOut": {
+      "type": "string"
+    },
+    "expectedOutWei": {
+      "type": "string"
+    },
+    "fee": {
+      "description": "Disclosed Quietwork fee (already reflected in expectedOut)",
+      "properties": {
+        "amountWei": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "bps": {
+          "type": "number"
+        },
+        "note": {
+          "type": "string"
+        },
+        "percent": {
+          "type": "number"
+        },
+        "receiver": {
+          "type": "string"
+        },
+        "takenFrom": {
+          "type": "string"
+        },
+        "token": {
+          "type": "string"
+        },
+        "venue": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "bps",
+        "percent",
+        "takenFrom",
+        "receiver",
+        "note"
+      ],
+      "type": "object"
+    },
+    "flatFee": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "flatFeeNativeWei": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "includesOperatingExpensesWei": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requestedAmountInWei": {
+      "type": "string"
+    },
+    "srcChain": {
+      "type": "string"
+    },
+    "srcChainId": {
+      "type": "integer"
+    },
+    "tokenIn": {
+      "properties": {
+        "address": {
+          "type": "string"
+        },
+        "decimals": {
+          "type": "integer"
+        },
+        "symbol": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "address",
+        "decimals",
+        "symbol"
+      ],
+      "type": "object"
+    },
+    "tokenOut": {
+      "properties": {
+        "address": {
+          "type": "string"
+        },
+        "decimals": {
+          "type": "integer"
+        },
+        "symbol": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "address",
+        "decimals",
+        "symbol"
+      ],
+      "type": "object"
+    },
+    "venue": {
+      "const": "debridge"
+    }
+  },
+  "required": [
+    "venue",
+    "srcChain",
+    "srcChainId",
+    "dstChain",
+    "dstChainId",
+    "tokenIn",
+    "tokenOut",
+    "amountIn",
+    "amountInWei",
+    "expectedOut",
+    "expectedOutWei",
+    "fee",
+    "deBridgeCosts"
+  ],
+  "type": "object"
+}

AddedOct 25, 2026

TDQS

A3.5/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 behavioral burden. It does valuable work itemising the total cost stack (0.1% affiliate fee, 4 bps protocol fee, flat native-coin fee, ~4 bps solver margin, solver gas), but it never states that this is a non-mutating price query, how long a quote stays valid, or that the result feeds debridge_build_tx — all critical for a quote tool.

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 front-loaded sentence that names the mechanism first, then the chain coverage, then the fee breakdown. Dense but every clause carries information; only the parenthetical fee enumeration is slightly cramped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. But for a 5-required-param quote tool with 40% schema coverage and no annotations, the description leaves quote validity, amount units, and the downstream build-tx handoff unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%, so the description must compensate, and it largely doesn't. The chain list merely restates the srcChain/dstChain enums, and the description says nothing about the 'amount' parameter — whether it is human-readable decimals, base units, or which token's decimals apply — which is the highest-risk ambiguity here.

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?

States a specific verb+resource (cross-chain EVM swap quote) and names the exact protocol (deBridge DLN), plus enumerates the six supported chains and gives a concrete example pair. It clearly distinguishes itself from single-chain quoting siblings like swap_quote, cow_quote, velora_quote and zerox_quote.

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?

The word 'cross-chain' implies this is the tool for bridging between chains rather than same-chain swaps, so the routing versus swap_quote is inferable. However, it never explicitly says when to use this instead of crosschain_rate or when to prefer debridge_build_tx directly, and no prerequisites are stated.

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

All Quietwork Swap 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?