Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

validateFGridInput

Validate futures grid bot input parameters and get allowable ranges for investment, profit, grid count, price bounds, leverage, and TP/SL to ensure valid bot creation.

Instructions

Validates the input parameters for creating a futures grid bot and returns the allowable ranges for each parameter (investment, profit, grid count, price bounds, leverage, TP/SL, etc.).

Use this endpoint before calling /v5/fgridbot/create to ensure parameters are within valid bounds. The response includes a check_code that indicates which parameter is out of range if validation fails.

Rate limit: 10 requests per second per UID.

Agent hint: Call this endpoint first to get valid parameter ranges before creating a grid bot. If check_code is non-zero, the specific validation error is indicated by the code value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
cell_numberYes
min_priceYes
max_priceYes
leverageYes
grid_typeYes
grid_modeYes
stop_loss_priceNo
take_profit_priceNo
tp_sl_typeNo
entry_priceNo
stop_loss_perNo
take_profit_perNo
trailing_stop_perNo
init_marginNo
move_up_priceNo
move_down_priceNo
Behavior4/5

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

Describes rate limit (10 requests/s/UID) and response includes check_code for error indication. No annotations provided, so description carries burden. Would benefit from mentioning read-only nature.

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?

Description is concise with four sentences and an agent hint. Front-loaded with main purpose. Rate limit info included. Could be slightly more compact but effective.

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?

Covers purpose, usage order, and error indication via check_code. Missing details on success response structure (e.g., the allowable ranges format) and no output schema to compensate.

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 has 0% description coverage and 17 parameters. Description lists some parameter categories (investment, profit, etc.) but does not explain each parameter. Partially compensates by stating validation returns ranges.

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?

The description clearly states it validates input parameters for creating a futures grid bot and returns allowable ranges. It distinguishes itself from sibling tools like createFGridBot and validateGridInput (likely for spot).

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 says to use before creating a grid bot and includes an agent hint. Does not explicitly state when not to use or compare to alternatives, but context implies futures grid only.

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