Skip to main content
Glama
gagarinyury

MCP Bitget Trading Server

by gagarinyury

disconnectWebSocket

Terminate WebSocket connections to stop real-time data streams from the Bitget cryptocurrency exchange, managing network resources effectively.

Instructions

Disconnect from WebSocket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case for the 'disconnectWebSocket' tool. It calls this.wsClient.disconnect() to disconnect the WebSocket and returns a success message.
    case 'disconnectWebSocket': {
      this.wsClient.disconnect();
      return {
        content: [
          {
            type: 'text',
            text: 'WebSocket disconnected',
          },
        ],
      } as CallToolResult;
    }
  • src/server.ts:248-256 (registration)
    Registration of the 'disconnectWebSocket' tool in the list of available tools returned by listTools. Defines the tool name, description, and empty input schema.
    {
      name: 'disconnectWebSocket',
      description: 'Disconnect from WebSocket',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
    },
  • Input schema for the 'disconnectWebSocket' tool, which requires no parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose effects like whether disconnection is immediate, if it affects other operations, error handling, or authentication needs, leaving significant gaps for a mutation tool.

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, direct sentence with no wasted words, making it highly efficient and front-loaded. Every word contributes to stating the core purpose without 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 this is a mutation tool (disconnecting implies change) with no annotations and no output schema, the description is incomplete. It lacks details on behavior, effects, or return values, failing to compensate for the missing structured information.

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?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description appropriately doesn't add parameter details, aligning with the baseline for zero-parameter tools.

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 ('Disconnect') and target resource ('from WebSocket'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getWebSocketStatus' or 'connectWebSocket' beyond the obvious verb difference, missing explicit scope or relationship context.

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 or prerequisites. It doesn't mention if it should be used after 'connectWebSocket', in error scenarios, or as part of cleanup, leaving usage context entirely implicit.

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