Skip to main content
Glama
Sign In

Quietwork Swap

by dev.workers.quietworklabs.qw-swap
OverviewDiscussionsAdmin

cow_quote

Gasless CoW Protocol market-order quote (ethereum, base, arbitrum, polygon, bsc; ERC-20 sell tokens). MEV-protected batch auction. Includes the same disclosed 0.1% fee as a CoW partner fee.

Input Schema

NameRequiredDescriptionDefault
chainYes
amountYes
senderNo
tokenInYesERC-20 symbol (WETH, USDC, ...) or 0x address; native coin not sellable on CoW
tokenOutYes
slippageBpsNo

Output Schema

NameRequiredDescriptionDefault
feeYesDisclosed Quietwork fee (already reflected in expectedOut)
chainYes
venueYes
minOutYes
senderNo
appDataNo
chainIdYes
quoteIdNo
tokenInYes
validToYes
amountInYes
receiverNo
tokenOutYes
verifiedNo
minOutWeiYes
amountInWeiYes
appDataHashYes
expectedOutYes
slippageBpsYes
expectedOutWeiYes
protocolFeeBpsNo
networkCostInSellTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "amountIn": {
+      "type": "string"
+    },
+    "amountInWei": {
+      "type": "string"
+    },
+    "appData": {
+      "type": "string"
+    },
+    "appDataHash": {
+      "type": "string"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "chainId": {
+      "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"
+    },
+    "minOut": {
+      "type": "string"
+    },
+    "minOutWei": {
+      "type": "string"
+    },
+    "networkCostInSellToken": {
+      "type": "string"
+    },
+    "protocolFeeBps": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "quoteId": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "receiver": {
+      "type": "string"
+    },
+    "sender": {
+      "type": "string"
+    },
+    "slippageBps": {
+      "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"
+    },
+    "validTo": {
+      "type": "integer"
+    },
+    "venue": {
+      "const": "cow"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "venue",
+    "chain",
+    "chainId",
+    "tokenIn",
+    "tokenOut",
+    "amountIn",
+    "amountInWei",
+    "expectedOut",
+    "expectedOutWei",
+    "fee",
+    "minOut",
+    "minOutWei",
+    "slippageBps",
+    "validTo",
+    "appDataHash"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

B3/5.0
Behavior2/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 usefully discloses MEV-protected batch-auction execution and a 0.1% partner fee, but never says whether quoting submits anything, whether quotes expire, or what permissions/signing are required — critical for a tool sitting next to cow_post_order.

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 tight sentences with the core purpose and chain scope front-loaded, plus fee disclosure. Slightly dense abbreviation ('ERC-20 sell tokens') but no wasted sentences.

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-value explanation isn't required, but the definition still leaves gaps on quote lifecycle and the semantics of amount/sender/slippageBps. Adequate as a minimum-viable definition, incomplete for a 6-parameter quoting tool.

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 17% across 6 parameters, so the description must compensate. It explains tokenIn's ERC-20-only constraint, but says nothing about 'amount' (units/decimals), 'sender', or 'slippageBps' (default 50, meaning unclear), leaving four parameters undocumented in both places.

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 states a specific verb+resource — 'Gasless CoW Protocol market-order quote' — and scopes it to five named chains and ERC-20 sell tokens. That distinguishes it from write-path siblings like cow_build_order and cow_post_order, but it doesn't explicitly contrast with the other quote siblings (swap_quote, zerox_quote, velora_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?

'Gasless' and 'ERC-20 sell tokens' imply usage constraints, and 'quote' implies a pre-trade read, but the description never states when to use this versus the sibling quote tools or that it precedes cow_build_order/cow_post_order. Usage is inferable rather than specified.

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

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