Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

freeze_sub_uid

Freeze or unfreeze a sub-account UID to control its trading activity. Set frozen parameter to 0 to unfreeze or 1 to freeze.

Instructions

Freeze or unfreeze a sub UID.

Args: sub_uid: Sub UID. frozen: 0: unfreeze, 1: freeze.

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_uid": "<sub_uid>",
      "frozen": "<frozen>"
    },
    "name": "freeze_sub_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
sub_uidYes
frozenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The description explains the binary effect (freeze/unfreeze) via the frozen parameter (0: unfreeze, 1: freeze). Since no annotations are provided, it carries the full burden, but it omits side effects, permissions, or reversibility.

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, using two sentences plus parameter explanations. Each sentence contributes, though the args section slightly breaks structure.

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

Completeness3/5

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

For a simple toggle tool with 2 parameters and no output schema, the description covers the basics but lacks fuller context on implications of freezing (e.g., whether the sub UID can still perform other operations).

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?

With 0% schema description coverage, the description adds meaning by clarifying frozen values (0: unfreeze, 1: freeze). sub_uid is briefly defined as 'Sub UID'. This provides useful context beyond the schema's bare types.

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 'Freeze or unfreeze a sub UID' clearly states the action on a specific resource, distinguishing it from sibling tools like create_sub_uid or delete_sub_uid. However, it lacks precision about what 'freeze' entails.

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 is provided on when to use this tool versus alternatives such as create_sub_uid or delete_sub_uid. There is no mention of prerequisites or scenarios for freezing/unfreezing.

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