Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getFMartLimit

Validate input parameters for futures Martingale bots and retrieve allowable ranges for price, leverage, margin, and more to avoid creation errors.

Instructions

Validates the input parameters for creating a futures Martingale bot and returns the allowable ranges for each parameter (price float percentage, add position ratio, add position count, initial margin, round TP percentage, stop-loss, entry price, leverage).

Use this endpoint before calling /v5/fmartingalebot/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: 100 requests per second per IP.

Agent hint: Call this endpoint first to get valid parameter ranges before creating a Martingale bot. If check_code is non-zero, the specific validation error is indicated by the code value. The response ranges tell you the exact min/max values allowed for each parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
martingale_modeYes
leverageYes
price_float_percentNo
add_position_percentNo
add_position_numNo
init_marginNo
round_tp_percentNo
sl_percentNo
entry_priceNo
need_to_slippageNo
app_nameNo
Behavior5/5

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

Despite no annotations, the description thoroughly discloses behavior: it is a read-only validation endpoint, returns ranges and check_code, and mentions rate limit. No contradictions.

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 concise and front-loaded with the core purpose. Rate limit detail could be in annotations but is acceptable here.

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 no output schema or annotations, the description covers usage context, response behavior, and rate limits. Lacks explicit success/error response structure but is adequate for the complexity.

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 most parameters but provides no detailed semantics for each. With 0% schema parameter descriptions, the listing adds some context but not enough to fully compensate.

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 the tool validates input parameters for creating a futures Martingale bot and returns allowable ranges. This distinguishes it from siblings like createFMartBot and closeFMartBot.

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 advises to call this endpoint before creating a bot, and describes the check_code mechanism for validation errors. Provides agent hint and rate limit 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