Bybit MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

validateGridInput

Read-only

Validate spot grid bot parameters before creation. Get acceptable ranges for investment, grid count, price bounds, and a check code that pinpoints any invalid input.

Instructions

Validates the input parameters for creating a spot grid bot, returning acceptable ranges for each parameter (investment amount, grid count, price bounds, stop-loss, take-profit, etc.) and a check code indicating any validation errors.

Use this endpoint before calling createGridBot to ensure parameters are within valid ranges. The response includes min/max ranges for every configurable field, plus a check_code enum that pinpoints the exact validation issue (if any).

Does not require authentication (guest mode, rate limit: 100 qps per IP).

Agent hint: Always call this before createGridBot to pre-validate parameters. The check_code field in the response tells you exactly what is wrong. A check_code of 0 means all parameters are valid.

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": {
      "symbol": "<symbol>",
      "cell_number": "<cell_number>",
      "min_price": "<min_price>",
      "max_price": "<max_price>",
      "total_investment": "<total_investment>"
    },
    "name": "validateGridInput"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes
`max_price`	Yes
`min_price`	Yes
`stop_loss`	No
`ts_percent`	No
`cell_number`	Yes
`entry_price`	No
`invest_mode`	No
`take_profit`	No
`limit_up_price`	No
`base_investment`	No
`enable_trailing`	No
`quote_investment`	No
`total_investment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.11Jun 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that no authentication is required, the guest-mode rate limit, the response structure (min/max ranges and check_code), and the meaning of check_code 0. This gives the agent concrete runtime expectations despite the absence of an output schema.

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 front-loaded with purpose and usage, then adds auth/rate-limit context and an agent hint in a compact form. There is slight redundancy because the agent hint restates 'call before createGridBot' and the check_code behavior already mentioned.

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?

For a 14-parameter validation tool with no output schema, the description covers the core flow: what the tool validates, when to call it, what the response conveys, and how to interpret a valid result. It would be stronger with an example response or the full check_code enum, but the essential guidance is present.

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 partially compensates by naming parameter categories such as investment amount, grid count, price bounds, stop-loss, and take-profit. However, it does not explain individual parameter semantics, units, or the invest_mode enum values, leaving the agent to infer details from names and schema types.

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?

States that it validates input parameters for creating a spot grid bot and describes the output: acceptable ranges plus a check code. It explicitly names createGridBot as the downstream tool, and 'spot grid bot' distinguishes it from future-grid variants like validateFGridInput.

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?

Explicitly instructs the agent to use this endpoint before calling createGridBot and repeats this in the agent hint. It does not mention when not to use it or explicitly compare it to validateFGridInput, so it lacks full exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server