Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_deposit_account

Configure your deposit account type by specifying account type (UNIFIED, SPOT, FUND) to direct funds to the correct account.

Instructions

Set deposit account type.

Args: account_type: UNIFIED, SPOT, FUND, etc.

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": {
      "account_type": "<account_type>"
    },
    "name": "set_deposit_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/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 indicates a mutation ('Set') but fails to mention side effects, permission requirements, or whether the action is reversible. The description is too sparse for a mutation tool.

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 very short, which is concise but lacks necessary detail. Every sentence is functional, but it could benefit from more structured information. It is not overlong, but it is under-specified.

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?

With no output schema and one parameter, the description is incomplete. It doesn't explain what happens after setting the account type (e.g., confirmation, impact on existing accounts). Compared to sibling tools, it does not help the agent differentiate when to use this tool.

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?

The description lists 'UNIFIED, SPOT, FUND, etc.' for the account_type parameter, which adds context beyond the schema (which has no enum or description). However, it doesn't explain the meaning or constraints of these values, leaving ambiguity. Schema coverage is 0%, so the description provides moderate value.

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 'Set deposit account type', which is a specific verb+resource combination. It distinguishes from other set_* tools by specifying 'deposit account'. However, it could be more explicit about what 'deposit account' refers to in the platform context.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or scenarios where this action is appropriate. The agent is left to infer usage without any hints.

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