Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

queryEscrowSubMembersV5

Read-only

Query paginated escrow sub-accounts for private wealth management. Retrieve fund management accounts managed by your trading team, including account status, mode, and next-cursor for navigating large datasets.

Instructions

Query escrow (fund management) sub-accounts in paginated format. Use trading team's API key.

Important notes:

  • Returns escrow sub-accounts (fund management type) associated with trading teams

  • Supports pagination using cursor-based navigation

  • Used specifically for Private Wealth Management scenarios

  • Only returns escrow sub-accounts bound to the requesting trading team

  • Trading team accounts can query their managed escrow relationships

Escrow Sub-accounts:

  • Type 6 custodial sub-accounts designated for fund management

  • Managed by trading teams on behalf of clients

  • Username displayed as "Private_Wealth_Management" for privacy

  • Have special permissions and restrictions

  • Cannot be directly accessed like normal sub-accounts

  • Relationship stored with escrow metadata in extension field

Pagination:

  • Uses cursor-based pagination for efficient large dataset handling

  • Default page size: 100 (maximum)

  • Returns nextCursor for fetching next page

  • nextCursor = 0 indicates last page reached

Required Permissions:

  • Trading team account API key

  • Appropriate escrow management permissions

Response includes:

  • Escrow sub-account UID

  • Account type (always 6 for escrow)

  • Account status

  • Account mode (Classic or UTA)

  • Remark/notes from extension field

  • Next cursor for pagination

Use Cases:

  • Trading teams managing client funds

  • Private wealth management operations

  • Institutional custody account listing

  • Fund management auditing

  • Escrow relationship monitoring

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": "queryEscrowSubMembersV5"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds rich behavioral detail: cursor-based pagination with nextCursor=0 as the terminal sentinel, default page size of 100, account type always 6, privacy-masked username, and the fact that these accounts cannot be accessed like normal sub-accounts. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with bolded sections and a front-loaded summary. However, it is somewhat repetitive: Private Wealth Management appears multiple times, and pagination details are covered in both the important notes and the dedicated pagination section, so it could be trimmed without losing essential information.

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

Completeness4/5

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

Given that there is no output schema, the description compensates by listing the response fields, pagination behavior, permissions, and use cases. Minor gaps remain, such as explicit parameter-name mapping and any rate-limit or error behavior, but for a read-only query tool the context is largely complete.

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

Parameters4/5

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

The schema has 0% description coverage, but the description compensates by explaining page size defaults/maximum and the meaning of nextCursor, including that nextCursor=0 indicates the last page. It does not explicitly map these explanations to the exact parameter names in a single place, but it is sufficient for invocation.

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 opens with a specific verb and resource: 'Query escrow (fund management) sub-accounts in paginated format.' It clearly differentiates from sibling tools like querySubMembersV5 by emphasizing that only escrow sub-accounts are returned and that it is used for Private Wealth Management scenarios.

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

Usage Guidelines4/5

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

It provides strong context: use the trading team API key, only escrow sub-accounts bound to the requesting trading team are returned, and typical use cases are listed. However, it does not explicitly name or contrast with the sibling querySubMembersV5 tool, so it stops short of full when-to-use versus alternative guidance.

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