Skip to main content
Glama

get_instruments_info

Retrieve detailed trading instrument specifications from Bybit, including category, symbol, status, and base coin data for informed cryptocurrency trading decisions.

Instructions

Get exchange information

Input Schema

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

Implementation Reference

  • Core handler function that executes the tool logic by calling Bybit's instruments-info API endpoint.
    async getInstrumentsInfo(
      category: string,
      symbol: string,
      status?: string,
      baseCoin?: string
    ): Promise<BybitResponse<{ list: InstrumentInfo[] }> | { error: string }> {
      const params: any = { category, symbol };
      if (status) params.status = status;
      if (baseCoin) params.baseCoin = baseCoin;
      return this.makeBybitRequest('/v5/market/instruments-info', 'GET', params);
    }
  • src/index.ts:457-482 (registration)
    Tool registration in the MCP server's ListTools handler, including name, description, and input schema.
    {
      name: 'get_instruments_info',
      description: 'Get exchange information',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Category (spot, linear, inverse, etc.)',
          },
          symbol: {
            type: 'string',
            description: 'Symbol (e.g., BTCUSDT)',
          },
          status: {
            type: 'string',
            description: 'Status',
          },
          baseCoin: {
            type: 'string',
            description: 'Base coin',
          },
        },
        required: ['category', 'symbol'],
      },
    },
  • MCP server dispatch handler that receives tool call and delegates to BybitService.getInstrumentsInfo.
    case 'get_instruments_info': {
      const result = await this.bybitService.getInstrumentsInfo(
        typedArgs.category,
        typedArgs.symbol,
        typedArgs.status,
        typedArgs.baseCoin
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Type definition for InstrumentInfo, used in the return type of getInstrumentsInfo, defining the output structure.
    export interface InstrumentInfo {
      symbol: string;
      contractType: string;
      status: string;
      baseCoin: string;
      quoteCoin: string;
      launchTime: string;
      deliveryTime: string;
      deliveryFeeRate: string;
      priceScale: string;
      leverageFilter: {
        minLeverage: string;
        maxLeverage: string;
        leverageStep: string;
      };
      priceFilter: {
        minPrice: string;
        maxPrice: string;
        tickSize: string;
      };
      lotSizeFilter: {
        maxOrderQty: string;
        maxMktOrderQty: string;
        minOrderQty: string;
        qtyStep: string;
        postOnlyMaxOrderQty: string;
      };
      unifiedMarginTrade: boolean;
      fundingInterval: number;
      settleCoin: string;
      copyTrading: string;
      upperFundingRate: string;
      lowerFundingRate: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states it 'gets' information, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, rate limits, pagination, error handling, or what the output format might be. For a tool with 4 parameters and no output schema, this leaves significant gaps in understanding how it behaves.

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 extremely concise with a single phrase 'Get exchange information', which is front-loaded and wastes no words. While it may be under-specified, it earns full marks for brevity and lack of redundancy.

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 tool has 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't compensate for the lack of structured data by explaining what information is returned, how to interpret results, or behavioral context. For a data retrieval tool with filtering parameters, this leaves the agent with insufficient guidance.

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?

Schema description coverage is 100%, so parameters are documented in the schema. The description adds no meaning beyond the schema—it doesn't explain how parameters interact (e.g., filtering by category and symbol together), provide examples, or clarify semantics like what 'status' or 'baseCoin' represent in context. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get exchange information' states the general purpose (retrieving data) but is vague about what specific information is retrieved. It doesn't specify what 'exchange information' includes (instrument details, specifications, etc.) or differentiate from sibling tools like get_tickers or get_orderbook that also retrieve exchange data. The verb 'get' is generic and the resource 'exchange information' is broad.

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 is provided on when to use this tool versus alternatives. The description doesn't mention context like needing instrument specifications, filtering by category/symbol, or comparing to siblings such as get_tickers (for price data) or get_orderbook (for market depth). There's no indication of prerequisites, exclusions, or typical use cases.

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