Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_risk_limit

Retrieve risk limit tiers for a trading pair. Specify symbol and category to view position risk constraints.

Instructions

Get risk limit info for a symbol.

Args: symbol: The trading pair, e.g., BTCUSDT. category: Product type: linear, inverse (default: linear).

Returns: Risk limit tiers for the symbol.

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>"
    },
    "name": "get_risk_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
categoryNolinear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states it returns risk limit tiers, failing to mention read-only nature, authentication needs, rate limits, or side effects. This leaves significant gaps for an agent.

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?

The description is very concise, front-loading the purpose and then listing parameters and returns in a structured format. No unnecessary words or repetition, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description is insufficient in explaining return values ('Risk limit tiers' is vague). It does not describe the structure or fields of the response. For a simple tool, the completeness is minimal.

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 adds some meaning beyond the schema by providing an example for symbol (BTCUSDT) and describing category as product type with default 'linear'. However, it does not enumerate accepted values formally, and the schema has 0% description coverage, so the description partially compensates but could be more precise.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves risk limit info for a symbol, specifying verb and resource. However, it does not explicitly differentiate from sibling tools like get_price_limit or confirm_risk_limit, which have different purposes.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool over alternatives, such as confirm_risk_limit for setting limits or get_price_limit for price limits. The description implies usage context but lacks explicit instructions or exclusions.

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

Deploy Server

Other Tools