Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

get_trade_history

Read-only

Query past trade executions using filters like category, symbol, order ID, and time range. Supports pagination for large datasets.

Instructions

Query trade execution history.

    Args:
        category: Product type - spot, linear, inverse, option
        symbol: Symbol name
        orderId: Order ID
        startTime: Start timestamp in milliseconds
        endTime: End timestamp in milliseconds
        limit: Limit per page (max 100, default 50)
        cursor: Pagination cursor
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
symbolNo
endTimeNo
orderIdNo
categoryYes
startTimeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Query' is consistent and adds the parameter list. However, it does not disclose any additional behaviors beyond what annotations provide.

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 description is a short docstring with a clear 'Args:' list. It front-loads the main verb and then lists parameters efficiently, with no unnecessary words.

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

Completeness3/5

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

Given the parameter count and 0% schema coverage, the description covers parameter meanings but lacks mention that 'category' is required, and does not help agents choose between this and similar tools like get_order_history.

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?

With 0% schema description coverage, the description compensates by explaining all 7 parameters (e.g., 'category: Product type - spot, linear, inverse, option'). This adds meaning beyond the schema's type/name.

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?

The description clearly states 'Query trade execution history', which is a specific verb and resource. It distinguishes from siblings like get_order_history and get_public_trades by focusing on execution history, but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_order_history or get_public_trades. The description only lists parameters without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/workspace/bybit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server