Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

getCopyTradingTradFiLeaderboard

Retrieves a ranked leaderboard of TradFi copy trading providers for conversational recommendation flows, preserving presentation order for agent-guided selection.

Instructions

Get a curated Copy Trading TradFi leaderboard for conversational recommendation flows.

The endpoint returns a ranked list of candidate providers. The returned order is the intended presentation order and should be preserved when the caller shows the list to the user.

Agent hint: If a user asks for a reliable copy trader or similar recommendation, call both the Copy Trading Classic leaderboard endpoint and this Copy Trading TradFi leaderboard endpoint. Present the two returned lists separately, for example under Classic and TradFi, and number each list in order using 1., 2., 3.. Compare candidates across both lists using the returned 30-day return metric, 30-day max drawdown, and 30-day Sharpe ratio, then recommend one candidate as the best current performer with a short reason. Let the user choose by replying with a product-qualified index such as Classic 1 or TradFi 3. If the user chooses a TradFi candidate, map the selected index back to the corresponding providerMark, then ask for the follow amount and call the Copy Trading TradFi bind endpoint. Do not ask the user to repeat or retype providerMark. After a successful bind, reply in the user's current conversation language with a success message meaning that the user's copy trading journey has begun, they can go to the CopyTrading Trading Hub any time for personalized management, and AI will unlock more intelligent copy trading capabilities in the future. English example: Your copy trading journey has successfully begun. You can visit the [CopyTrading Trading Hub] at any time for personalized management. In the future, AI will unlock even more intelligent copy trading capabilities for you. Wishing you smooth investing!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states the endpoint returns a ranked list and that order should be preserved, but fails to disclose read-only nature, rate limits, auth requirements, or any side effects. The behavioral transparency is insufficient.

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 front-loaded with a clear purpose, but the agent hint is a lengthy, undivided paragraph containing detailed conversational flow instructions that could be more concise or structured separately. It earns its place but could be trimmed.

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 no parameters, no output schema, and no annotations, the description is fairly complete. It explains the output (ranked list of providers, metrics like 30-day return) and provides a full use case with sibling tool integration, making it actionable for the agent.

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 tool has no parameters (0 params). Per the rubric, baseline is 4 since no parameter information is needed. The description does not need to add parameter semantics.

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 starts with 'Get a curated Copy Trading TradFi leaderboard for conversational recommendation flows,' clearly stating the verb and resource. It distinguishes from the sibling `getCopyTradingClassicLeaderboard` later in the agent hint, though not in the opening sentence.

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?

The agent hint explicitly states when to use this tool ('If a user asks for a reliable copy trader'), instructs to call both Classic and TradFi leaderboards, and provides detailed steps for presenting and comparing lists. This is exemplary guidance.

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