Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getChatMessages

Read-only

Retrieve chat messages for a Bybit P2P order by providing the order ID and page size, letting you review buyer-seller communications for trade coordination and dispute resolution.

Instructions

Get chat messages for a P2P order.

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": {
      "orderId": "<orderId>",
      "size": "<size>"
    },
    "name": "getChatMessages"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
orderIdYes
currentPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

B3/5.0
Behavior2/5

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

Annotations already mark the operation read-only, and the description adds no behavioral context beyond that: no mention of what is returned, pagination behavior, or order-ownership prerequisites. With no extra contextual disclosure beyond the annotations, this is a gap.

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?

A single, front-loaded sentence with no filler. It communicates the verb, resource, and scope efficiently.

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?

For a tool with no output schema and 0% parameter descriptions, the description is too thin for an agent to be confident about return shape, pagination, and parameter values. It is a viable starting point but not complete enough to prevent a misinvocation (e.g., passing size in the wrong format).

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

Parameters2/5

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

Schema description coverage is 0%, and the description only ties the resource to 'a P2P order', weakly implying the orderId parameter. It does not explain size or currentPage semantics (e.g., page size, paging, string encoding), so required parameters remain underdocumented.

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 uses a specific verb ('Get') and resource ('chat messages') scoped to 'a P2P order', so the core operation is clear. It does not explicitly differentiate this from the sibling 'readMessages' tool, which could be confused by name alone.

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

Usage Guidelines3/5

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

The phrase 'for a P2P order' implies the tool should be used when chat messages tied to a specific P2P order are needed, so the context is inferable. However, it gives no explicit when/when-not guidance and names no alternatives such as readMessages.

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