Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getTradeHistory

Read-only

Retrieve RFQ trade execution history with optional filters for IDs, trader type, and status, including per-leg details like orderId, fees, mark price, and rejection reasons.

Instructions

Query RFQ trade execution history with optional filtering by IDs, trader type, and status. Supports cursor-based pagination. Results include detailed per-leg execution information.

Field query priority: rfqId > rfqLinkId, quoteId > quoteLinkId. The rfqLinkId and quoteLinkId parameters restrict results to the last 3 months.

Rate Limit: 50 requests per second.

Agent hint: Use this to check trade execution results after calling Execute Quote. Contains detailed per-leg info including orderId, execFee, markPrice, and rejection details. rfqLinkId and quoteLinkId only search the last 3 months. TradFi: use category=spot for xStock execution records, category=linear for equity/commodity perpetual executions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getTradeHistory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
rfqIdNo
cursorNo
statusNo
quoteIdNo
rfqLinkIdNo
traderTypeNoquote
quoteLinkIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses rate limiting (50 rps), cursor-based pagination, field query priority, the 3-month search restriction on link IDs, and the detailed per-leg fields returned. This adds substantial behavioral context that an agent cannot infer from annotations alone.

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

Conciseness3/5

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

The core purpose is front-loaded and the format is readable, but the description is longer than necessary: the 3-month rfqLinkId/quoteLinkId restriction and the per-leg field list are each stated twice. This redundancy prevents a higher score.

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 tool with 8 optional parameters and no output schema, the description covers filtering, pagination, rate limits, time constraints, and output contents. It is not fully complete because there is no structured return shape and the unsupported 'category' parameter creates ambiguity, but it provides enough context for correct use in the intended Execute Quote workflow.

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 description coverage is 0%, so the description carries the burden, and it compensates well by explaining pagination semantics, field query priority, and the time-restricted behavior of rfqLinkId/quoteLinkId. It is slightly incomplete because not every parameter is individually explained and it mentions a 'category' parameter that does not appear in the input schema, which could mislead an agent.

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?

The description opens with a specific action and resource: 'Query RFQ trade execution history' with optional filters. The agent hint 'Use this to check trade execution results after calling Execute Quote' pins down the exact workflow, which separates it from generic history tools like queryTradeHistory or getOrderHistory in the sibling list.

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?

It gives explicit context for when to call the tool ('after calling Execute Quote') and operational constraints such as field query priority and the 3-month limitation for rfqLinkId/quoteLinkId. It does not explicitly name alternatives or state when not to use the tool, but the context is clear enough for an agent to select it appropriately.

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

Deploy Server

Other Tools