Quietwork Swap

debridge_build_tx

Build an unsigned deBridge DLN cross-chain order transaction (plus ERC-20 approval tx if needed) for sender to sign on the source chain. Same fees as debridge_quote. Returns orderId for tracking.

Input Schema

Name	Required	Description
`amount`	Yes
`sender`	Yes	0x wallet that signs; also the order authority on both chains
`tokenIn`	Yes
`dstChain`	Yes
`srcChain`	Yes
`tokenOut`	Yes
`recipient`	No	0x receiver on dstChain (default sender)

Output Schema

Name	Required	Description
`tx`	Yes
`fee`	Yes	Disclosed Quietwork fee (already reflected in expectedOut)
`next`	No
`note`	No
`track`	Yes
`venue`	Yes
`status`	Yes
`flatFee`	No
`orderId`	Yes
`tokenIn`	Yes
`amountIn`	Yes
`approval`	No	Present for ERC-20 input tokens
`dstChain`	No
`srcChain`	No
`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"
+      ]
+    },
+    "approval": {
+      "description": "Present for ERC-20 input tokens",
+      "properties": {
+        "amount": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "required_if_allowance_below": {
+          "type": "string"
+        },
+        "spender": {
+          "type": "string"
+        },
+        "token": {
+          "type": "string"
+        },
+        "tx": {
+          "properties": {
+            "chainId": {
+              "type": "integer"
+            },
+            "data": {
+              "type": "string"
+            },
+            "from": {
+              "type": "string"
+            },
+            "gas": {
+              "type": "string"
+            },
+            "to": {
+              "type": "string"
+            },
+            "value": {
+              "description": "0x hex wei",
+              "type": "string"
+            }
+          },
+          "required": [
+            "chainId",
+            "to",
+            "data",
+            "value",
+            "from"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "required_if_allowance_below",
+        "token",
+        "spender",
+        "tx"
+      ],
+      "type": "object"
+    },
+    "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"
+      ]
+    },
+    "next": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "orderId": {
+      "type": "string"
+    },
+    "requestedAmountInWei": {
+      "type": "string"
+    },
+    "srcChain": {
+      "type": "string"
+    },
+    "srcChainId": {
+      "type": "integer"
+    },
+    "status": {
+      "type": "string"
+    },
+    "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"
+    },
+    "track": {
+      "type": "string"
+    },
+    "tx": {
+      "properties": {
+        "chainId": {
+          "type": "integer"
+        },
+        "data": {
+          "type": "string"
+        },
+        "from": {
+          "type": "string"
+        },
+        "gas": {
+          "type": "string"
+        },
+        "to": {
+          "type": "string"
+        },
+        "value": {
+          "description": "0x hex wei",
+          "type": "string"
+        }
+      },
+      "required": [
+        "chainId",
+        "to",
+        "data",
+        "value",
+        "from"
+      ],
+      "type": "object"
+    },
+    "venue": {
+      "const": "debridge"
+    }
+  },
+  "required": [
+    "venue",
+    "srcChainId",
+    "dstChainId",
+    "tokenIn",
+    "tokenOut",
+    "amountIn",
+    "amountInWei",
+    "expectedOut",
+    "expectedOutWei",
+    "fee",
+    "deBridgeCosts",
+    "orderId",
+    "tx",
+    "track",
+    "status"
+  ],
+  "type": "object"
+}

AddedOct 25, 2026

TDQS

A3.7/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 burden and does disclose the important traits: the output is unsigned, an approval transaction may be bundled, fees match debridge_quote, and an orderId is returned for tracking. It does not mention whether the transaction expires, whether it reserves liquidity, or any prerequisite ordering (quote-first), which matters for a transaction-building 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?

Three short sentences, front-loaded with the core action and the approval-tx caveat. No filler, though the fee-parity sentence is more useful than the return-value sentence given an output schema exists.

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?

The presence of an output schema excuses it from explaining return values, and the signing flow is well described. However, for a 7-parameter cross-chain build tool with 29% schema coverage, the missing parameter and prerequisite detail leaves the definition only minimally sufficient.

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 description coverage is only 29% — just 'sender' and 'recipient' are documented in the schema — and the description adds nothing about amount units, token address format, or the meaning of srcChain/dstChain selection. Four required parameters (amount, tokenIn, tokenOut, and the chain pair) remain semantically thin, so the description fails to compensate for the low coverage.

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 and resource: builds an unsigned deBridge DLN cross-chain order transaction, including an ERC-20 approval tx when needed. The phrase 'Same fees as debridge_quote' implicitly separates it from the sibling quote tool, so an agent can tell what it produces versus what a quote produces.

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?

Clearly positions the tool at the signing step ('for sender to sign on the source chain') and distinguishes it from debridge_quote by noting fee parity, which implies this is the execute-path counterpart to a quote. It also hints that the returned orderId feeds debridge_order_status. It stops short of explicitly saying a quote must precede it or when not to use it.

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?