Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_broker_sub_deposit_record

Retrieve deposit records for broker sub accounts. Optionally filter by sub member ID, coin, or limit the number of records.

Instructions

Get broker sub account deposit records.

Args: sub_member_id: Sub member ID (optional). coin: Filter by coin (optional). limit: Number of records (default: 50).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_broker_sub_deposit_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
sub_member_idNo
coinNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states 'Get records' but fails to disclose behavioral traits such as read-only nature, pagination behavior, or any side effects. The description is too minimal to inform the agent about the tool's operation.

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 short and front-loaded with the purpose. It uses a clear 'Args:' block. It is concise without wasted words, though it could be slightly more structured.

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?

Given the complexity (many sibling tools, 3 parameters, no output schema), the description is insufficient. It does not explain the return format, any boundaries on 'limit', or how to differentiate this from other deposit record tools. The description lacks completeness for effective tool selection and invocation.

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?

Schema coverage is 0%, so description adds meaning. Each parameter is briefly described: 'Sub member ID (optional)', 'Filter by coin (optional)', 'Number of records (default: 50)'. This provides context beyond the schema titles, but descriptions are minimal and could be more detailed (e.g., format of sub_member_id).

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 broker sub account deposit records' with verb 'Get' and specific resource. It differentiates from siblings like 'get_sub_deposit_records' by specifying 'broker sub account', but the distinction could be more explicit.

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 vs alternatives like 'get_deposit_records' or 'get_sub_deposit_records'. The description lacks any context about appropriate 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