Skip to main content
Glama
zereight

Bithumb MCP Server

post_ticker_user

Retrieve a user's recent cryptocurrency transaction history from Bithumb exchange for a specified asset, providing private account activity details.

Instructions

Get member's recent virtual asset transaction information (Private)

Input Schema

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

Implementation Reference

  • The core handler function for the 'post_ticker_user' tool. It prepares parameters and calls the private requestInfo method to fetch user's ticker data from Bithumb API endpoint '/info/ticker'.
    public async postTickerUser(orderCurrency: string): Promise<IPostTickerUser> {
      const params = {
        order_currency: orderCurrency,
      };
      const res = <IPostTickerUser>await this.requestInfo('ticker', params);
      return res;
    }
  • src/index.ts:156-166 (registration)
    Registers the 'post_ticker_user' tool in the MCP server with its name, description, and input schema validation.
    {
      name: 'post_ticker_user',
      description: 'Get member\'s recent virtual asset transaction information (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['orderCurrency']
      }
    },
  • Dispatch case in the main MCP tool call handler that invokes the specific postTickerUser method.
    case 'post_ticker_user':
      result = await this.bithumbApi.postTickerUser(args.orderCurrency as string);
      break;
  • TypeScript interface defining the expected response structure for the post_ticker_user tool (output schema).
    export interface IPostTickerUser extends IBithumbResponse {
      data: ITickerUser;
    }
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. It mentions '(Private)' which hints at authentication requirements, but fails to detail rate limits, response format, pagination, or whether this is a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 with no wasted words. It front-loads the core purpose and includes a relevant qualifier, making it appropriately sized and structured for quick comprehension.

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 transaction data and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'recent' means, the format of returned information, or how it differs from sibling tools, leaving the agent with incomplete 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 the single required parameter 'orderCurrency'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for adequate but not enhanced coverage.

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 ('Get') and resource ('member's recent virtual asset transaction information'), with the qualifier '(Private)' indicating access restrictions. However, it doesn't explicitly differentiate from siblings like 'get_transaction_history' or 'post_user_transactions', which appear related.

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 such as 'get_transaction_history' or 'post_user_transactions'. The '(Private)' hint implies authentication needs but doesn't specify prerequisites or exclusions, leaving usage context vague.

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