Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_WITHDRAWALS

Retrieve withdrawal records from your Upbit account, filtered by currency and status. Use it to track and review your withdrawal history.

Instructions

List withdrawals (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNo
stateNo
pageNo
limitNo

Implementation Reference

  • The handler/execute function for the LIST_WITHDRAWALS tool. Calls ensurePrivateEnabled(), builds a query with pagination params, signs a JWT token, and fetches /withdraws from Upbit API, returning JSON-stringified results.
    export const listWithdrawalsTool = {
    	name: "LIST_WITHDRAWALS",
    	description: "List withdrawals (requires private API)",
    	parameters: paramsSchema,
    	execute: async ({ currency, state, page, limit }: Params) => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const query = {
    			page,
    			limit,
    			currency,
    			state,
    		};
    		const token = signJwtToken(query);
    		const data = await fetchJson<unknown>(client, "/withdraws", {
    			params: query,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema for the LIST_WITHDRAWALS tool parameters: optional currency, optional state, page (default 1), limit (default 50, max 100).
    const paramsSchema = z
    	.object({
    		currency: z.string().optional(),
    		state: z.string().optional(),
    		page: z.number().int().min(1).default(1),
    		limit: z.number().int().min(1).max(100).default(50),
    	})
    	.strict();
  • src/index.ts:42-42 (registration)
    Registration of the LIST_WITHDRAWALS tool on the MCP server via server.addTool().
    server.addTool(listWithdrawalsTool);
  • src/index.ts:21-21 (registration)
    Import of listWithdrawalsTool from the list-withdrawals.ts file in src/index.ts.
    import { listWithdrawalsTool } from "./tools/list-withdrawals.js";
Behavior2/5

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

No annotations, so description must carry burden. It only states 'requires private API' but does not disclose pagination, sorting, or effect of state parameter on behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single short sentence, no fluff, but could be more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters, no output schema, no annotations, and no parameter descriptions, the description is severely incomplete for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and description adds no information about the meaning or allowed values for currency, state, page, or limit parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states the tool lists withdrawals, a specific verb+resource. It distinguishes from siblings like LIST_DEPOSITS and CANCEL_WITHDRAWAL.

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?

Only mentions 'requires private API', which is a prerequisite, but no guidance on when to use it versus alternatives like GET_WITHDRAWAL, and no exclusion criteria.

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/IQAIcom/mcp-upbit'

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