Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getHoldToEarnProduct

Read-only

Find available Hold-to-Earn products on Bybit. Retrieve current listings to compare earning options without authentication.

Instructions

Query available Hold-to-Earn product listings. No authentication required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getHoldToEarnProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as read-only and open-world, and the description adds the useful behavioral detail that no authentication is required. That is legitimate context beyond the annotations, though it does not describe return shape or pagination.

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 two short sentences with no wasted words. It front-loads the action and resource, then adds the only relevant precondition (no authentication), making it appropriately compact.

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 parameterless, read-only listing tool, the description is largely sufficient: it states what is queried and that no auth is needed. The main omission is guidance on choosing between this and similar sibling endpoints, but that is not critical for invoking the tool correctly.

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 zero parameters and the input schema is empty, so there is no parameter ambiguity to clarify. A baseline of 4 is appropriate because the description does not need to add parameter semantics that do not exist.

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 clearly states a specific verb ('Query') and resource ('available Hold-to-Earn product listings'), so an agent can understand the tool's function. It does not explicitly differentiate from sibling Earn-product endpoints like getEarnProduct or getAdvanceEarnProduct, but the Hold-to-Earn naming narrows the scope.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus the many similar product-listing siblings, and it names no alternatives or exclusions. The 'No authentication required' note is an access fact, not a usage condition.

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