Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_spread_recent_trades

Retrieve recent public trades for a spread symbol. Specify symbol and optional limit for number of records.

Instructions

Get spread trading recent public trades.

Args: symbol: Spread symbol. limit: Number of records (default: 50).

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": {
      "symbol": "<symbol>"
    },
    "name": "get_spread_recent_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The description mentions that the tool returns 'public trades', which is a key behavioral trait. However, it does not disclose other important behaviors such as rate limits, data freshness, pagination, or error handling. Given no annotations, the description provides minimal but useful transparency.

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?

The description is extremely concise with one main line and two parameter descriptions. Every sentence earns its place with no unnecessary text.

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

Completeness2/5

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

Despite low complexity, the description omits crucial details: no output schema, no mention of return format, pagination, or how 'recent' is defined. A user would need additional documentation to use the tool effectively.

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

Parameters3/5

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

The description adds meaning to parameters by explaining 'symbol: Spread symbol' and 'limit: Number of records (default: 50)', which is helpful since schema coverage is 0%. However, it does not elaborate on format or constraints.

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 clearly states 'Get spread trading recent public trades', which specifies the verb (get), resource (spread trading recent public trades), and distinguishes it from siblings like get_spread_trade_history which may not be limited to recent or public.

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 no guidance on when to use this tool versus alternatives such as get_spread_trade_history or get_recent_trade. It lacks context about intended use cases or exclusions.

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