Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getPredictionTimelineStages

Retrieve the tournament stages timeline for sports prediction events. Shows which stages are Done, Active, or Upcoming to identify the current phase for predictions.

Instructions

Query the tournament stages timeline for a sports prediction event. Returns all stages (Group Stage, Round of 32, Round of 16, Quarter-finals, Semi-finals, Final) with their current status.

AI agent uses this to understand the current tournament phase and navigate to the relevant stage for predictions.

Agent hint: Use this to get the tournament stage timeline for FIFA 2026 (eventType=1). Returns which stages are Done/Active/Upcoming. Use stageCode from here in getPredictionGroupStageDetail to get group standings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventTypeNo
Behavior4/5

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

The description explains the return (stages with status Done/Active/Upcoming) and is a read-only query. No annotations exist, so the description carries the burden; it adequately discloses behavior but could explicitly state it is read-only and safe.

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?

Three concise sentences front-load purpose, then example, then agent hint. No fluff; every sentence adds value.

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 simple one-parameter query, the description is fairly complete: explains return, gives example, and links to sibling. Lacks details on output format and error handling, but the tool's simplicity mitigates this.

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?

The schema has one string parameter without description (0% coverage). The description adds meaning by giving a concrete example (eventType=1 for FIFA 2026), helping the agent understand the value space. However, it does not enumerate all valid eventType values.

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 it queries the tournament stages timeline for a sports prediction event, listing the specific stages returned. It distinguishes from sibling tools like getPredictionGroupStageDetail.

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?

Provides explicit when-to-use: to understand the current tournament phase and navigate to the relevant stage. Includes a concrete example (FIFA 2026, eventType=1) and references the sibling tool getPredictionGroupStageDetail for further steps.

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