Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_mmp

Configure Market Maker Protection (MMP) parameters for a specified base coin, including time window, frozen period, trade quantity limit, and delta limit.

Instructions

Set Market Maker Protection (MMP) parameters.

Args: base_coin: Base coin, e.g., BTC. window: Time window in ms. frozen_period: Frozen period in ms. qty_limit: Trade quantity limit. delta_limit: Delta limit.

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": {
      "base_coin": "<base_coin>",
      "window": "<window>",
      "frozen_period": "<frozen_period>",
      "qty_limit": "<qty_limit>",
      "delta_limit": "<delta_limit>"
    },
    "name": "set_mmp"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_coinYes
windowYes
frozen_periodYes
qty_limitYes
delta_limitYes

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 present, and the description does not disclose side effects, required permissions, or whether the operation is reversible. It only states the action without behavioral context.

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 brief and lists parameters clearly, but the structure is somewhat fragmented. It could be more integrated and efficient without losing clarity.

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 the tool's complexity (setting protection parameters), the description fails to provide context on what happens after setting, confirmation, error handling, or interaction with existing parameters.

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 description coverage is 0%, so the description provides basic parameter semantics (e.g., 'Base coin, e.g., BTC', 'Time window in ms'), but lacks details like valid ranges, constraints, or format, offering only minimal value over the schema.

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 Market Maker Protection (MMP) parameters.' which specifies a verb and resource. However, it does not differentiate from the sibling tool 'reset_mmp' which also handles MMP but with a different action.

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 like 'reset_mmp' or 'get_mmp_state'. The description lacks any contextual or conditional usage information.

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