Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getAdvanceEarnProduct

Read-only

Query available Bybit Advance Earn product listings by category, coin, or duration to identify suitable earning opportunities.

Instructions

Query available Advance Earn product listings. No authentication required.

Rate Limit: 50 req/s (IP)

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": {
      "category": "<category>"
    },
    "name": "getAdvanceEarnProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNo
categoryYes
durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful operational constraints not present in the annotations: no authentication required and a 50 req/s IP-based rate limit. However, it does not disclose response shape, pagination, or filtering behavior.

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 compact and well-structured: a clear purpose sentence followed by two concise, useful operational notes. No filler or redundancy.

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

Completeness3/5

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

For a simple listing query, the purpose and schema are mostly sufficient. But with 0% schema description coverage and no output schema, the description should at least hint at what coin and duration mean and what the response represents, which it omits.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden of explaining parameters, but it does not mention 'coin', 'category', or 'duration'. The schema's enum for category and required marker help, but the description itself adds no parameter meaning.

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 states a specific verb ('Query') and resource ('Advance Earn product listings'), making the tool's purpose clear. It doesn't explicitly differentiate from siblings like getAdvanceEarnProductExtraInfo, but 'listings' does distinguish it from order and position tools.

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

Usage Guidelines3/5

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

Usage is implied by the description: query available Advance Earn product listings. It provides operational context via 'No authentication required' and a rate limit, but it does not explicitly state when to prefer this tool over related alternatives such as getAdvanceEarnProductExtraInfo or getEarnProduct.

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