Skip to main content
Glama

Quote a trade

quote
Read-onlyIdempotent

Prices a trade now in both markets Semiosis trades in, the Civic Pool and its Pons launch curve, read at the same block: ETH for Semiosis (side "buy", amount in ETH) or Semiosis for ETH (side "sell", amount in Semiosis). Uses the market that gives more (market auto, the default; the Civic Pool keeps a near tie within 0.5%, since its fee goes to the treasury), or the one named. Gives the market used and why, both markets’ quotes, the expected amount out, the minimum at the chosen slippage, the fee, the price impact and its warnings. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "side": "<side>",
      "amount": "<amount>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
amountYesIn whole units as a decimal string: ETH for a buy, Semiosis for a sell, such as "0.01".
marketNoWhere to trade. auto (the default) quotes the Civic Pool and Semiosis’s Pons launch curve at the same block and uses the one that gives more; the Civic Pool keeps a near tie (within 0.5%), since its fee goes to the treasury, and a buy that would close the curve is never sent to it (the quote gives markets.pons.maxBuyEth). civic or pons uses that market; civic keeps every trade on the CivicRouter, with its deadline.
slippage_bpsNoSlippage in basis points, 1 to 500 (100 = 1%). Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint), and the description adds substantial behavior beyond them: both venues read at the same block, the selection rule for auto, the treasury-fee tie-break, the curve-closing guard, and the fact that price-impact warnings are surfaced. That is exactly the routing and risk context an agent needs before quoting.

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?

Front-loaded with the action and scope, then dosages of detail in a logical order (sides, market selection, returned fields). It is a dense single paragraph with some restatement of the market parameter's text, which costs it a point but nothing is truly wasted.

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?

There is no output schema, and the description compensates by enumerating the return payload: market used and why, both market quotes, expected amount out, minimum at the chosen slippage, fee, price impact and warnings. Combined with the annotations, an agent has everything needed to call and interpret this tool.

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

Parameters4/5

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

With 75% schema coverage the schema already documents amount, market and slippage in detail; the description adds the mapping of 'side' to amount units (ETH for buy, Semiosis for sell) and reinforces auto as default. Some of this duplicates the market parameter's own description, so the added meaning is real but partly redundant.

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 ('Prices a trade now') and immediately scopes it to the two markets (Civic Pool and Pons launch curve) with both trade directions defined. The closing 'Read-only' plus 'quote' framing implicitly separates it from the write-path sibling build_transaction, so an agent can pick the right tool without opening a schema.

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?

Gives clear conditions: default 'market auto' quotes both venues at the same block and picks the better one, with the explicit 0.5% near-tie rule and the caveat that a curve-closing buy is never routed to Pons. It does not explicitly say 'use build_transaction afterwards to execute', so the step in the workflow is implied rather than named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources