Bull OTC

bull_quote_status

Use as BUYER or SELLER to check a quote and its onchain deal: status (pending, confirmed, funded, released), dealId, counter, who has funded. Poll this or use webhooks. Only the two parties can read it. 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_quote_status"
  }
}

Input Schema

Name	Required	Description
`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.1/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 much of it: it discloses the access constraint (only the two parties), the status lifecycle, and the two-step signed-read flow where the first call returns a message and the second replays the same arguments plus timestamp and signature. It stops short of stating rate limits or pagination behavior for a polling 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?

Front-loaded with the caller role and the core check, then the constraints, then the signing protocol, all in four sentences with no filler. Dense but slightly telegraphic phrasing costs it the top mark.

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 annotations, no output schema, and only four parameters, the definition covers everything an agent needs: audience, the returned fields, access control, refresh strategy, and the complete two-step signing handshake.

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 would be 3, but the description adds real meaning to `signature` and `timestamp` by explaining the first-call/second-call protocol and that they must be left empty initially. That is semantics the schema alone would not make obvious.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('check a quote and its onchain deal') and enumerates the returned fields (status, dealId, counter, funded parties). It is clearly a read tool, though it never explicitly distinguishes itself from siblings like bull_get_quotes or bull_get_deal.

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?

Says explicitly to use it as BUYER or SELLER, that only the two parties can read it, and that you can 'Poll this or use webhooks' rather than something else. No explicit exclusions against the retrieval siblings are given, so it falls short of a full when/when-not statement.

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?