Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_sub_deposit_records

Retrieve sub account on-chain deposit records with optional coin filter and record limit.

Instructions

Get sub account on-chain deposit records.

Args: sub_member_id: Sub UID. coin: Filter by coin (optional). 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": {
      "sub_member_id": "<sub_member_id>"
    },
    "name": "get_sub_deposit_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
sub_member_idYes
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 are provided, so the description must disclose behavioral traits. It only states the action ('Get on-chain deposit records') without mentioning idempotency, read-only nature, authorization requirements, or rate limits. The lack of detail leaves the agent uninformed about side effects or constraints.

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 concise and front-loaded with the core action. It uses a brief docstring format with clear parameter explanations. No superfluous content.

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 no output schema and no annotations, the description should describe return values, pagination, or record structure. It only mentions parameters, leaving the agent guessing about the response format. For a simple list retrieval, more context is needed.

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?

With 0% schema description coverage, the description adds meaning by briefly explaining parameters: sub_member_id is 'Sub UID', coin is 'Filter by coin (optional)', limit is 'Number of records (default: 50)'. This is helpful but minimal; it does not elaborate on formats or allowed values.

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 it retrieves sub account on-chain deposit records, which is a specific verb-resource combination. While it doesn't explicitly differentiate from sibling tools like get_broker_sub_deposit_record, the name and context provide sufficient clarity.

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 versus alternatives (e.g., get_broker_sub_deposit_record for broker sub-accounts). The description only lists parameters, lacking context on prerequisites 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