Bull OTC

bull_accept_quote

Use as a BUYER to accept a quote. Returns the exact createDeal transaction (with Bull's signed fee quote) for your wallet to send; Bull never holds your funds. Then call bull_attach_deal with the dealId from the DealCreated event. Safe to call again to refresh the fee quote. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.

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": {
      "quoteId": "<quoteId>",
      "address": "<address>"
    },
    "name": "bull_accept_quote"
  }
}

Input Schema

Name	Required	Description
`address`	Yes	Your wallet address (the buyer or seller). Required.
`quoteId`	Yes	Quote id.
`payAsset`	No	"base" to pay in ETH (default) or "alt" to pay in the stablecoin.
`signature`	No	EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call.
`timestamp`	No	From the previous bull_* response. Leave empty on the first call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior5/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 so well: it discloses that Bull never holds funds, that the output is an unsigned createDeal transaction for the caller's wallet to send, the two-step sign-then-resubmit flow, and idempotent re-call behavior for quote refresh. These are exactly the non-obvious traits an agent needs before invoking 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?

Four short, front-loaded sentences: role, return value, follow-up call, then re-call/signing semantics. Every clause carries information, though the terse 'Signed:' label is slightly compressed and the signing rules could be sequenced more explicitly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing both response branches (a message to sign on the first call, a createDeal transaction afterward) and the source of the dealId. It leaves minor gaps around quote-state prerequisites (e.g. expired or already-accepted quotes) and the downstream effect of `payAsset` on the resulting deal.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by explaining that `timestamp` and `signature` come from the previous call and are supplied alongside identical arguments on the second invocation. This clarifies the parameter relationship across calls rather than merely restating field 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?

States a specific verb and resource ('accept a quote') plus an explicit role gate ('Use as a BUYER'), which distinguishes it from sibling actions like bull_reject_quote, bull_counter_quote, and bull_revise_quote. An agent can identify the operation without opening the 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 applicability via the BUYER role restriction and prescribes the next step ('Then call bull_attach_deal with the dealId from the DealCreated event'), plus notes it is safe to repeat to refresh the fee quote. It stops short of naming the sibling actions a non-buyer should use instead, so it is clear context rather than full when/when-not routing.

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

All Bull OTC 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?