Highwire

Quote a trade

quote_trade

Read-onlyIdempotent

Preview a higher.fun coin buy or sell before trading: get expected output, minimum received at your slippage, price impact, fee split, and Highwire's 0.3% fee from read-only data.

Instructions

Quote a buy (by SOL in) or a sell (by tokens in) of a higher.fun coin, wherever it trades now: the LaunchLab bonding curve, or its Raydium CPMM pool after graduation. Returns the expected output, the minimum at the given slippage, price impact, the fees split by who receives them under the coin's fee mode, and Highwire's 0.3% trade fee (highwireFee), which a trade built through Highwire carries. Reads 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": {
      "mint": "<mint>",
      "side": "<side>"
    },
    "name": "quote_trade"
  }
}

Input Schema

Name	Required	Description
`sol`	No	For a buy: SOL to spend.
`mint`	Yes	The coin's mint address (base58). higher.fun mints usually end in 'high'.
`side`	Yes	buy spends SOL for tokens; sell spends tokens for SOL.
`tokens`	No	For a sell: whole tokens to sell (supply is 1B).
`slippage_bps`	No	Slippage for the minimum out, in bps (100 = 1%).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for going further: it discloses automatic venue routing (curve vs graduated pool), the exact composition of the response (expected out, min-out at slippage, price impact, fee split by fee mode, Highwire's 0.3%), and that highwireFee only applies to trades built through Highwire.

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 mode/venue distinction is front-loaded and every clause carries information (venue routing, return contents, fee ownership). It is one long sentence with heavy nesting, but no filler.

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 correctly compensates by enumerating the returned fields, and it covers venue selection, fee attribution, and read-only behavior. Nothing an agent needs to invoke or interpret the quote is missing.

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 description coverage is 100%, so the schema already documents mint format, side enum, sol/tokens exclusivity, and slippage_bps semantics. The description adds only a restatement of the buy-vs-sell input convention, so the baseline 3 applies.

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 ('Quote a buy ... or a sell ... of a higher.fun coin') and immediately distinguishes the two modes (SOL in vs tokens in) and the two venues (LaunchLab bonding curve vs Raydium CPMM). An agent can tell this apart from build_trade and get_coin_trades without opening any schema.

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 description establishes context — this is a read-only price preview, and the implied next step is building a trade that carries highwireFee — but it never explicitly says when to call this versus build_trade, nor any precondition such as requiring a valid mint or minimum size. Usage is inferable rather than stated.

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