Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

queryStrategyList

Retrieve and filter trading strategies by status, symbol, type, or time range using pagination for efficient review and monitoring.

Instructions

Retrieve a list of strategies with filtering options and pagination support.

When to use:

  • Check status of specific strategy by strategyId

  • Monitor all running strategies

  • Review completed strategies for performance analysis

  • Filter strategies by symbol, type, or time period

Query modes:

  1. Exact lookup: Provide strategyId to get specific strategy details

  2. Filtered list: Use symbol, category, strategyType, status filters

  3. Time range: Use beginTimeE0 and endTimeE0 for date range queries

  4. Paginated: Use cursor and pageSize for large result sets

Strategy Status Values:

  • 2: Running - Strategy is actively executing

  • 3/4: Terminated - Strategy has stopped (check terminateType for reason)

  • 5: Paused - Strategy is temporarily paused

  • 6: Untriggered - Conditional strategy waiting for trigger price

Important notes:

  • Strategies are sorted by creation time (newest first)

  • Use cursor for pagination (nextCursor in response)

  • Maximum pageSize: 50

  • Default pageSize: 20

  • Time filters use Unix timestamp in seconds

Agent hint: Use this endpoint when user asks about their strategies, wants to check strategy status, or needs to review strategy performance. Common queries: "show my strategies", "check TWAP strategy status", "what strategies are running on BTCUSDT".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategyIdNo
statusNo
symbolNo
categoryNo
strategyTypeNo
beginTimeE0No
endTimeE0No
pageSizeNo
cursorNo
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses sorting order (newest first), pagination (cursor, max 50, default 20), time filter format (Unix seconds), and explains status values (2-6). It does not mention destroy effects (none expected) or rate limits, but as a read query it is transparent enough.

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 sections: intro, when to use, query modes, status values, important notes, agent hint. It is front-loaded with purpose. While verbose, every sentence serves a purpose. Minor redundancy in 'Query modes' could be tightened, but it remains clear and scannable.

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 9 parameters, no output schema, and no annotations, the description covers key aspects: purpose, usage modes, status value meanings, pagination limits, sorting order. It does not describe the response structure or potential errors, but for an agent to select and invoke the tool, the provided context is sufficient.

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 coverage is 0%, so the description must add meaning. It explains the four query modes, mapping to parameters: exact lookup (strategyId), filtered list (symbol, category, strategyType, status), time range (beginTimeE0, endTimeE0), paginated (cursor, pageSize). It also details status values. It does not explain category or strategyType enums nor the cursor format, but overall provides substantial semantic enrichment.

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 a list of strategies with filtering and pagination. It distinguishes from sibling tools like createTwapStrategy or stopStrategy by focusing on querying. The verb 'retrieve' and resource 'strategies' are specific.

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 'When to use' section lists concrete scenarios (check status, monitor running, review performance, filter by symbol/type/time). The 'Query modes' map to different parameter combinations. An agent hint provides example queries. It lacks explicit when-not-to-use or comparisons with sibling tools like getGridDetail, but it's still strong.

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