Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_index_price_components

Retrieve the components of a specific index price by providing the index name, such as BTCUSDT.

Instructions

Get index price components.

Args: index_name: Index name, e.g., BTCUSDT.

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": {
      "index_name": "<index_name>"
    },
    "name": "get_index_price_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
index_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must bear the burden of disclosing behavior. It only states 'Get index price components' without detailing auth needs, rate limits, or whether the operation is read-only. The example implies a specific format, but behavioral traits are absent.

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 extremely concise (two lines) and front-loaded with the purpose. It avoids fluff, but could be slightly expanded to include basic behavioral info without losing conciseness.

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

Completeness2/5

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

Given no output schema and a simple tool with one parameter, the description is too minimal. It does not describe what the return values are (e.g., list of components with prices), leaving the agent to guess the output structure.

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

Parameters3/5

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

The schema has 0% description coverage, but the description provides an example value 'BTCUSDT' which adds format hint beyond the schema's generic string type. However, it does not explain constraints like allowed patterns or case sensitivity.

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 'Get index price components' clearly states the verb 'Get' and the resource 'index price components'. It distinguishes itself from siblings like 'get_index_price_kline' by focusing on components rather than kline data. However, it could be more explicit about what 'components' includes.

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?

No guidance on when to use this tool versus alternatives such as 'get_index_price_kline' or 'get_mark_price_kline'. The context of index price components is not contrasted with other price-related tools.

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