Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

validateGridInput

Validates input parameters for a spot grid bot, returning acceptable ranges and error codes. Use before creating the bot to ensure parameter validity.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
cell_numberYes
min_priceYes
max_priceYes
total_investmentYes
stop_lossNo
take_profitNo
entry_priceNo
base_investmentNo
quote_investmentNo
invest_modeNo
ts_percentNo
enable_trailingNo
limit_up_priceNo
Behavior5/5

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

Discloses the response includes acceptable ranges and a check_code, explains what check_code=0 means, and notes no authentication required and rate limit (100 qps per IP). No annotations are present, so the description fully compensates.

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

Conciseness5/5

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

Description is a single well-structured paragraph with front-loaded purpose, usage, response details, and agent hint. Every sentence adds value without redundancy.

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 the tool's complexity (14 params, no output schema), the description covers purpose, usage, response behavior, auth, and rate limit. It lacks detailed error scenarios but is largely complete for a validation 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?

Schema coverage is 0%, and while the description lists parameter categories ('investment amount, grid count, price bounds, stop-loss, take-profit, etc.'), it does not explain all 14 parameters individually or add meaning beyond the schema names and 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?

Description clearly states 'Validates the input parameters for creating a spot grid bot' with a specific verb and resource, and distinguishes itself from sibling createGridBot by emphasizing its pre-validation role.

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

Usage Guidelines5/5

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

Explicitly says 'Use this endpoint before calling createGridBot' and includes an agent hint directing to always call it before creation, providing clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bybit-exchange/trading-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server