Skip to main content
Glama

Get CoW Protocol Quote

cow_get_quote
Read-only

Retrieve a price and fee quote for a trade on CoW Protocol, including estimated amounts and a prepared order structure.

Instructions

Get a price and fee quote for a potential trade on CoW Protocol.

This returns the estimated amounts, fees, and a prepared order structure that can be signed and submitted.

Args:

  • network: The blockchain network (mainnet, gnosis, arbitrum, base, avalanche, polygon, bnb, sepolia)

  • sellToken: Token to sell (address or symbol like 'WETH')

  • buyToken: Token to buy (address or symbol like 'USDC')

  • kind: 'sell' for market sell (exact sell amount), 'buy' for market buy (exact buy amount)

  • amount: The amount in wei as a string

  • from: The trader's address (used for balance/allowance simulation)

  • receiver: Optional address to receive bought tokens (defaults to 'from')

  • partiallyFillable: Whether the order can be partially filled (default: false)

  • slippageBps: Optional slippage tolerance in basis points

Returns the quoted order with:

  • sellAmount, buyAmount, feeAmount

  • expiration timestamp

  • quote ID for tracking

  • Whether the quote was verified via simulation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesThe address that would create the order (used for simulation)
kindYesOrder kind: 'sell' for exact sell amount, 'buy' for exact buy amount
amountYesThe amount in wei (as string). For 'sell' this is sellAmount, for 'buy' this is buyAmount
networkNoThe network to get a quote onmainnet
buyTokenYesThe token to buy (address or symbol like 'USDC', 'COW')
receiverNoOptional receiver address for the bought tokens
sellTokenYesThe token to sell (address or symbol like 'WETH', 'USDC')
slippageBpsNoSlippage tolerance in basis points (e.g., 50 = 0.5%)
partiallyFillableNoWhether the order can be partially filled
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds transparency by detailing what the tool returns: estimated amounts, fees, an order structure, quote ID, and simulation verification. This provides context beyond the annotations.

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?

The description is well-structured with clear sections for Args and Returns. It is appropriately detailed but contains some redundancy with the schema, slightly reducing conciseness. Overall, it is efficient and front-loaded.

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 no output schema, the description fully explains the return values (sellAmount, buyAmount, feeAmount, expiration, quote ID, verification status). All 9 parameters are covered, and the tool's purpose is completely specified.

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 coverage is 100%, so the baseline is 3. The description includes an Args section that restates parameter descriptions but adds minimal new meaning (e.g., example tokens). It does not significantly enhance understanding beyond the schema's existing descriptions.

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 purpose: 'Get a price and fee quote for a potential trade on CoW Protocol.' It specifies the verb 'get' and resource 'quote', and distinguishes from sibling tools like cow_get_auction and cow_get_order by focusing on quotes for potential trades.

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 implies usage context: it returns estimated amounts and a prepared order structure that can be signed and submitted. It does not explicitly state when to use vs alternatives, but the context is clear that this is for obtaining a quote before trading.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saturn-dbeal/cow-skill'

If you have feedback or need assistance with the MCP directory API, please join our Discord server