Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

queryGridDetail

Read-only

Retrieve a spot grid bot's full state and performance using its grid ID, including symbol, price range, profit metrics, arbitrage count, status, stop settings, and close reason.

Instructions

Retrieves comprehensive details of a spot grid bot including symbol, price range, investment amount, profit metrics (total profit, grid profit, APR), arbitrage count, status, stop-loss/take-profit settings, trailing stop configuration, and close reason (if closed).

Use this when you need to check the current state, performance, or configuration of a specific grid bot. The grid_id is obtained from createGridBot response or grid list queries.

Rate limit: 10 qps per UID.

Agent hint: Use this to answer questions about a specific grid bot's performance or status. The grid_id is a numeric ID returned by createGridBot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grid_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.20
    • addedInput schema / properties / grid_id / anyOf
      Added value: +[
+  {
+    "pattern": "^[0-9]+$",
+    "type": "string"
+  },
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  }
+]
    • removedInput schema / properties / grid_id / type
      Removed value: -"integer"
  2. First observedv2.1.11

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true already present, the description adds useful behavioral context: it is a read operation, it has a rate limit of 10 qps per UID, and it returns close reason if closed. These details go beyond the annotations and help set expectations for the agent.

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

Conciseness3/5

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

The description is well-structured and front-loaded with the purpose, but there is redundancy: 'Use this' appears twice, and the grid_id origin is repeated in both the usage paragraph and the agent hint. It could be tightened without losing information.

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?

For a single-parameter read operation with no output schema, the description is quite complete: it lists the returned fields, states the rate limit, and explains how to obtain grid_id. It does not cover error cases or empty results, but those are minor gaps given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It successfully explains that grid_id is a numeric ID and tells the agent where to obtain it (createGridBot response or grid list queries). This adds meaningful meaning beyond the raw schema.

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 retrieves comprehensive details of a spot grid bot, enumerating the specific data fields (symbol, price range, profit metrics, status, etc.). It uses a specific verb-resource pair and differentiates from sibling grid-related tools by explicitly scoping to 'spot grid bot'.

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 'Use this when you need to check the current state, performance, or configuration of a specific grid bot' and explains that grid_id comes from createGridBot or grid list queries. It does not explicitly name alternatives or when not to use this tool, but the guidance is clear and actionable.

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