Skip to main content
Glama

get_tickers

Retrieve real-time trading data for specific cryptocurrency pairs on Bybit, including price, volume, and market movements, to support informed trading decisions.

Instructions

Get ticker information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory (spot, linear, inverse, etc.)
symbolYesSymbol (e.g., BTCUSDT)

Implementation Reference

  • MCP tool handler for 'get_tickers' in the switch statement of CallToolRequestSchema. Calls BybitService.getTickers and returns JSON stringified result.
    case 'get_tickers': {
      const result = await this.bybitService.getTickers(typedArgs.category, typedArgs.symbol);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:122-138 (registration)
    Tool registration in ListToolsRequestSchema response, including name, description, and input schema requiring category and symbol.
      name: 'get_tickers',
      description: 'Get ticker information',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Category (spot, linear, inverse, etc.)',
          },
          symbol: {
            type: 'string',
            description: 'Symbol (e.g., BTCUSDT)',
          },
        },
        required: ['category', 'symbol'],
      },
    },
  • Core implementation of getTickers in BybitService class. Makes authenticated GET request to Bybit API /v5/market/tickers endpoint.
    async getTickers(category: string, symbol: string): Promise<BybitResponse<{ list: TickerData[] }> | { error: string }> {
      return this.makeBybitRequest('/v5/market/tickers', 'GET', { category, symbol });
    }
  • TypeScript interface defining the structure of ticker data returned from Bybit API.
    export interface TickerData {
      symbol: string;
      lastPrice: string;
      prevPrice24h: string;
      price24hPcnt: string;
      highPrice24h: string;
      lowPrice24h: string;
      volume24h: string;
      turnover24h: string;
      fundingRate: string;
      openInterest: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get ticker information' implies a read-only operation, but it doesn't specify whether this is a real-time or cached query, rate limits, authentication requirements, or what happens on errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with just three words, making it front-loaded and waste-free. However, this brevity borders on under-specification, as it lacks necessary detail for clarity and completeness, slightly reducing its effectiveness despite the efficient structure.

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 the complexity of financial data tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'ticker information' includes, how results are formatted, or any behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 description adds no meaning beyond what the input schema provides. With schema description coverage at 100%, the schema already documents both parameters ('category' and 'symbol') adequately. This meets the baseline score of 3, as the description doesn't need to compensate but also doesn't enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get ticker information' is a tautology that essentially restates the tool name 'get_tickers' with minimal elaboration. It specifies the verb 'Get' and resource 'ticker information', but lacks specificity about what ticker information entails (e.g., price, volume, bid/ask) and doesn't differentiate from siblings like 'get_instruments_info' or 'get_orderbook', which may provide overlapping or related data.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions, and with siblings like 'get_instruments_info' and 'get_orderbook' that might serve similar purposes, this omission leaves the agent without direction on tool selection.

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/kondisettyravi/mcp-bybit-node'

If you have feedback or need assistance with the MCP directory API, please join our Discord server