Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getFMartLimit

Read-only

Validate futures Martingale bot input parameters and retrieve allowable ranges for price float, add position ratio, margin, take-profit, stop-loss, entry price, and leverage before creating a bot.

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
app_nameNo
leverageYes
sl_percentNo
entry_priceNo
init_marginNo
martingale_modeYes
add_position_numNo
need_to_slippageNo
round_tp_percentNo
price_float_percentNo
add_position_percentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds useful behavior beyond that: the response includes check_code to identify the out-of-range parameter, and it provides exact min/max ranges. It also documents the rate limit of 100 requests per second per IP.

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 well-structured with front-loaded purpose, followed by usage guidance, response semantics, rate limit, and an agent hint. It is mostly efficient, though the 'Use this endpoint before calling' statement and the later 'Agent hint: Call this endpoint first' are somewhat redundant.

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 there is no output schema, the description adequately covers what to expect: allowable ranges and a check_code on validation failure. It provides enough context for an agent to call the endpoint correctly in the creation workflow, though it could be more explicit about the full set of request 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 carries the burden of explaining parameters. It maps most input fields to human-readable meanings (price float percentage, add position ratio, add position count, initial margin, round TP percentage, stop-loss, entry price, leverage). However, it does not cover all 12 parameters, notably symbol, martingale_mode, app_name, and need_to_slippage, and does not clarify value formats.

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 opens with a specific verb and resource: 'Validates the input parameters for creating a futures Martingale bot' and states the returned output as allowable ranges. It clearly differentiates itself from creation tools like createFMartBot by explicitly positioning it as a pre-creation validation endpoint.

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?

The description explicitly says to use this endpoint before calling /v5/fmartingalebot/create and the agent hint reinforces calling it first to get valid ranges. It lacks explicit when-not-to-use or alternative-tool guidance, but for this domain the intended workflow is clear.

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