Skip to main content
Glama
gagarinyury

MCP Bitget Trading Server

by gagarinyury

subscribeToTicker

Subscribe to real-time price updates for cryptocurrency trading pairs on Bitget exchange to monitor market movements.

Instructions

Subscribe to real-time ticker updates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol
instTypeNoInstrument type (default: SPOT)

Implementation Reference

  • src/server.ts:257-268 (registration)
    Registration of the 'subscribeToTicker' tool in the MCP server's listTools handler, including name, description, and input schema definition.
    {
      name: 'subscribeToTicker',
      description: 'Subscribe to real-time ticker updates',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Trading pair symbol' },
          instType: { type: 'string', enum: ['SPOT', 'UMCBL'], description: 'Instrument type (default: SPOT)' }
        },
        required: ['symbol']
      },
    },
  • Handler implementation for the 'subscribeToTicker' tool in the MCP server's CallToolRequestSchema switch statement. Parses arguments and delegates to WebSocket client's subscribe method.
    case 'subscribeToTicker': {
      const { symbol, instType = 'SPOT' } = args as any;
      this.wsClient.subscribe('ticker', symbol, instType);
      return {
        content: [
          {
            type: 'text',
            text: `Subscribed to ticker updates for ${symbol} (${instType})`,
          },
        ],
      } as CallToolResult;
    }
  • Core subscribe method in BitgetWebSocketClient that constructs and sends the WebSocket subscription message for the ticker channel to Bitget exchange.
    subscribe(channel: string, symbol: string, instType: 'SPOT' | 'UMCBL' | 'DMCBL' = 'SPOT'): void {
      const subscription: WSSubscription = {
        op: 'subscribe',
        args: [{
          instType,
          channel,
          instId: symbol
        }]
      };
    
      const subKey = `${instType}:${channel}:${symbol}`;
      this.subscriptions.add(subKey);
    
      if (this.isConnected && this.ws) {
        logger.debug('Subscribing to channel', { channel, symbol, instType });
        this.ws.send(JSON.stringify(subscription));
      } else {
        logger.warn('WebSocket not connected, subscription will be sent on reconnect', { channel, symbol });
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal insight. It implies a real-time streaming operation but doesn't cover critical aspects like whether this requires authentication, how updates are delivered (e.g., via WebSocket events), potential rate limits, or how to stop subscriptions (e.g., using 'unsubscribeFromChannel'). This leaves significant gaps for agent decision-making.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, achieving optimal 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 the complexity of a real-time subscription tool with no annotations or output schema, the description is insufficiently complete. It lacks details on behavioral traits (e.g., streaming mechanics, error handling), integration with sibling tools (e.g., WebSocket management), and expected outputs (e.g., how updates are received). This leaves the agent with inadequate context for effective use.

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 input schema has 100% description coverage, clearly documenting both parameters ('symbol' and 'instType') with details like enum values and defaults. The description adds no additional parameter semantics beyond what the schema provides, such as format examples for 'symbol' or implications of 'instType' choices. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 the action ('Subscribe') and resource ('real-time ticker updates'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getTicker' (which likely retrieves static data) or 'subscribeToOrderBook' (which handles a different data stream), missing an opportunity for clearer distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active WebSocket connection via 'connectWebSocket'), exclusions, or comparisons to siblings like 'getTicker' (for one-time data) or 'unsubscribeFromChannel' (for stopping subscriptions), leaving usage context ambiguous.

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/gagarinyury/MCP-bitget-trading'

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