Bull OTC

bull_revise_quote

Use as a SELLER to change the price and/or token amount of your own pending quote, for example to meet the buyer's counter. Returns the new terms. The buyer then accepts with bull_accept_quote. Works only while the quote is pending. 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_revise_quote"
  }
}

Input Schema

Name	Required	Description
`price`	No	New total price in ETH (optional).
`tokens`	No	New token amount (optional).
`address`	Yes	Your wallet address (the buyer or seller). Required.
`quoteId`	Yes	Quote id.
`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.4/5.0

Behavior4/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 well: it discloses the SELLER-only restriction, the pending-only window, the return value ('Returns the new terms'), and the two-step signed flow (first call returns a message to sign, second call repeats the same arguments plus timestamp and signature). It does not say what happens on failure (expired quote, wrong caller, signature mismatch) or whether the buyer is notified, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the role and the action, then the outcome, the alternative, the precondition, and the signing protocol in that order. Every sentence carries distinct information with no repetition.

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?

For a 6-parameter mutation with no annotations and no output schema, the description covers role, timing, return value, and the signing handshake, which is what an agent needs to invoke it correctly. Failure modes and the effect on the counterparty are left unstated, a minor gap given the high schema coverage.

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 parameters are already documented; the description adds only that price and tokens are jointly optional ('and/or') and that the second call repeats the same arguments. That is useful but marginal beyond the schema's own 'Leave empty on the first call' notes, 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 (change the price and/or token amount of your own pending quote) and adds a caller-role constraint (SELLER) plus a scope constraint (pending only). This distinguishes it clearly from bull_counter_quote (buyer-side) and bull_accept_quote, which are named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use scenario ('to meet the buyer's counter'), an explicit precondition ('Works only while the quote is pending'), and names the follow-up alternative ('The buyer then accepts with bull_accept_quote'). An agent can pick between this and the counter/accept siblings without opening another schema.

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?