Skip to main content
Glama
zereight

Bithumb MCP Server

get_assets_status

Check deposit and withdrawal status for cryptocurrencies on Bithumb exchange to monitor transaction progress and confirm fund movements.

Instructions

Get asset deposit/withdrawal status (Public)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderCurrencyYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • The core handler function in the ApiBithumb class that executes the logic for the get_assets_status tool by making a public API request to Bithumb's assetsstatus endpoint.
    public async getAssetsStatus(
      orderCurrency: string,
    ): Promise<IGetAssetsStatus> {
      const res = <IGetAssetsStatus>(
        await this.requestPublic('assetsstatus', orderCurrency)
      );
      return res;
    }
  • src/index.ts:96-106 (registration)
    Registers the get_assets_status tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'get_assets_status',
      description: 'Get asset deposit/withdrawal status (Public)',
      inputSchema: {
        type: 'object',
        properties: {
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['orderCurrency']
      }
    },
  • TypeScript interface defining the response structure for the getAssetsStatus API call.
    interface IAssetsStatus {
      deposit_status: number;
      withdrawl_status: number;
    }
    
    export interface IGetAssetsStatus extends IBithumbResponse {
      data: IAssetsStatus[];
    }
  • Dispatcher case in the MCP CallToolRequestSchema handler that invokes the getAssetsStatus method with tool arguments.
    case 'get_assets_status':
      result = await this.bithumbApi.getAssetsStatus(args.orderCurrency as string);
      break;
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 for behavioral disclosure. While 'Get' implies a read operation and '(Public)' suggests no authentication needed, the description doesn't specify rate limits, error conditions, response format, or whether this includes historical or real-time data. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 at just 5 words, with no wasted language. It's front-loaded with the core purpose. However, the extreme brevity comes at the cost of completeness, which is reflected in other dimension scores.

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?

For a tool with no annotations, no output schema, and multiple potentially overlapping sibling tools, the description is insufficient. It doesn't explain what 'status' means (pending, completed, failed?), what timeframes are covered, or how this differs from related tools. The '(Public)' qualifier is helpful but doesn't compensate for other gaps.

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 the schema already fully documents the single parameter 'orderCurrency'. The description doesn't add any additional context about parameter usage beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('asset deposit/withdrawal status'), and includes the scope qualifier '(Public)'. However, it doesn't explicitly differentiate this from sibling tools like 'get_balance' or 'get_transaction_history' which might also relate to asset status.

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. With multiple sibling tools like 'get_balance' and 'get_transaction_history' that could overlap with asset status concepts, there's no indication of what distinguishes this specific tool or when it should be preferred.

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/zereight/bithumb-mcp'

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