Bithumb MCP Server

get_transaction_history

Retrieve recent cryptocurrency transaction records from the Bithumb exchange to track trading activity and analyze market movements for informed decision-making.

Instructions

Get recent transaction history (Public)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coinCode`	Yes	Cryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

src/bitThumb/index.ts:77-85 (handler)

Core handler function implementing the get_transaction_history tool by calling Bithumb's public transaction_history endpoint.

public async getTransactionHistory(
  coinCode: string,
): Promise<IGetTransactionHistory> {
  const param = `${coinCode}_${this.paymentCurrency}`;
  const res = <IGetTransactionHistory>(
    await this.requestPublic('transaction_history', param)
  );
  return res;
}

src/index.ts:85-94 (registration)

Tool registration in the MCP server, defining name, description, and input schema.

{
  name: 'get_transaction_history',
  description: 'Get recent transaction history (Public)',
  inputSchema: {
    type: 'object',
    properties: {
      coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
    },
    required: ['coinCode']
  }

src/index.ts:303-304 (handler)

MCP CallToolRequestHandler dispatch case that invokes the specific tool handler.

case 'get_transaction_history':
  result = await this.bithumbApi.getTransactionHistory(args.coinCode as string);

src/bitThumb/types/transaction-history.interface.ts:11-13 (schema)
TypeScript interface defining the output structure for getTransactionHistory response.
```
export interface IGetTransactionHistory extends IBithumbResponse {
  data: ITransactionHistory[];
}
```

src/index.ts:88-93 (schema)

JSON schema defining the input parameters for the tool (coinCode required).

inputSchema: {
  type: 'object',
  properties: {
    coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
  },
  required: ['coinCode']

Tool Definition Quality

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states it's for public data without detailing behavioral traits like rate limits, data recency, pagination, or error conditions. It doesn't disclose whether it's read-only (implied by 'Get') or other operational constraints, leaving significant gaps.

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 zero waste—it directly states the purpose and scope ('Public'). It's appropriately sized and front-loaded, earning its place 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?

For a tool with no annotations, no output schema, and 1 parameter, the description is incomplete. It lacks details on return values, error handling, or behavioral context (e.g., what 'recent' means, data format), making it inadequate for full agent understanding despite low complexity.

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 coverage is 100%, with the parameter 'coinCode' well-described in the schema. The description adds no additional parameter semantics beyond implying it filters by cryptocurrency, which is already covered. 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.

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('recent transaction history'), with the qualifier '(Public)' suggesting it retrieves public rather than user-specific data. It distinguishes from siblings like 'post_user_transactions' (likely user-specific) and 'get_balance' (different resource), though it doesn't explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for public transaction history, but doesn't specify when to use this versus alternatives like 'post_user_transactions' or other data-fetching tools. It provides basic context (public data) but lacks explicit guidance on prerequisites, timing, or exclusions.

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

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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