Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_recent_trade

Retrieve recent public trades for any product category on Bybit, including spot, linear, inverse, and option. Specify symbol and limit to refine results.

Instructions

Get recent public trades.

Args: category: Product type: spot, linear, inverse, option. symbol: Symbol (required for spot/linear/inverse). limit: Number of records (default: 60 for spot, 500 for others).

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": {
      "category": "<category>"
    },
    "name": "get_recent_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes
symbolNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies read-only and explains parameter behaviors (e.g., symbol required for spot/linear/inverse). However, it does not mention rate limits, pagination, or what 'recent' means.

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?

Very concise, front-loaded with purpose, uses efficient bullet-like format. Every sentence adds value with no waste.

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?

Covers basic parameters and purpose, but lacks details on public vs private distinction, time range, and pagination. Given sibling tools, more context would help differentiation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds significant meaning: explains category values, symbol requirement per category, and limit defaults. This fully compensates for the lack of schema documentation.

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 'Get recent public trades' with a specific verb and resource. However, it does not differentiate from sibling tools like get_trade_history or get_rfq_public_trades.

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?

The description provides parameter details but no guidance on when to use this tool vs alternatives like get_trade_history or get_rfq_public_trades. No when-not-to-use or context for selection.

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