Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_symbol_price

Retrieve the current market price for a cryptocurrency pair. Specify the trading symbol and optional product category to get price data from Bybit.

Instructions

Get the current price of a cryptocurrency pair.

Args: symbol: The trading pair, e.g., BTCUSDT. category: Product type: spot, linear, inverse (default: spot).

Returns: Price information from Bybit.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_symbol_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
categoryNospot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description must disclose behavior. It states returns 'Price information' but does not specify what fields are returned (e.g., bid, ask, last) or any real-time/delay characteristics. This is adequate for a simple tool but lacks details.

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 concise with two short paragraphs, front-loading the purpose. No redundant information, but could be more structured with bullet points.

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 price retrieval tool, the description covers the basic purpose and parameters. However, without an output schema, the return value is vague. Given the complexity and sibling tools like get_tickers, more context on output format would enhance completeness.

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?

Schema coverage is 0%, so the description must add meaning. It provides an example (BTCUSDT) for symbol and explains category as product type with default spot. This adds value beyond the schema's minimal type definitions.

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 the tool gets the current price of a cryptocurrency pair, with a specific verb 'Get' and a well-defined resource. It differentiates from siblings like get_tickers which might provide multiple prices.

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?

The description implies the tool is for a single symbol price query but does not explicitly state when to use it versus alternatives like get_tickers or get_orderbook. No when-not-to-use or alternative guidance is provided.

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