Retrieve historical orders for Bybit Earn products like Dual Assets and Smart Leverage. Filter by order ID, product, or time to track investment activity.
Query your order history. Requires Earn permission on the API key.
Rate Limit: 10 req/s (UID)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | ||
| endTime | No | ||
| orderId | No | ||
| category | Yes | ||
| productId | No | ||
| startTime | No | ||
| orderLinkId | No |
Changes observed during successful MCP inspections.
v2.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description adds useful behavioral context beyond those: the Earn permission requirement and the 10 req/s rate limit. This is exactly the kind of auth and rate-limit context that helps an agent use the tool safely, though it does not describe pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured, front-loading the purpose and then presenting permission and rate-limit info. However, it is succinct to the point of omitting important operational details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 8 parameters, no output schema, and no parameter semantics, this description is not complete enough for an agent to reliably select or invoke the tool. It covers permission and rate limit, but leaves filtering, pagination, and category meaning entirely unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it provides no explanation of category, cursor, limit, orderId, productId, startTime, endTime, or orderLinkId. The required category parameter's enum values are listed in the schema, but their meaning is unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action and object ('Query your order history') but does not specify that this is Advance Earn order history. Given numerous sibling tools like getEarnOrderHistory, getOrderHistory, and getOrderList, the description alone does not differentiate this tool from those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a prerequisite ('Requires Earn permission') and a rate limit, but gives no guidance on when to use this tool versus related order-history tools. No alternatives or exclusionary conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.