Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

CREATE_WITHDRAWAL

Withdraw digital assets from your Upbit exchange account by specifying currency, amount, destination address, and network type using the private API.

Instructions

Request a digital asset withdrawal (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
amountYes
addressYes
net_typeYes
secondary_addressNo
transaction_typeNo

Implementation Reference

  • The complete implementation of the CREATE_WITHDRAWAL tool, including name, description, parameters schema reference, and the execute handler that performs the withdrawal via Upbit's private API.
    export const createWithdrawalTool = {
    	name: "CREATE_WITHDRAWAL",
    	description: "Request a digital asset withdrawal (requires private API)",
    	parameters: paramsSchema,
    	execute: async (params: Params) => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const token = signJwtToken(params);
    		const data = await fetchJson<unknown>(client, "/withdraws/coin", {
    			method: "POST",
    			data: params,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema defining the input parameters for the CREATE_WITHDRAWAL tool.
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		amount: z.string(),
    		address: z.string(),
    		net_type: z.string(),
    		secondary_address: z.string().optional(),
    		transaction_type: z.enum(["default", "internal"]).optional(),
    	})
    	.strict();
  • src/index.ts:40-40 (registration)
    Registration of the CREATE_WITHDRAWAL tool with the FastMCP server.
    server.addTool(createWithdrawalTool);
  • src/index.ts:7-7 (registration)
    Import statement for the CREATE_WITHDRAWAL tool implementation.
    import { createWithdrawalTool } from "./tools/create-withdrawal.js";
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions 'requires private API' (hinting at authentication needs) but lacks critical behavioral details: whether this is a destructive/mutative operation (likely yes, given 'Request'), rate limits, confirmation steps, or what happens on success/failure. For a withdrawal tool with financial implications, this is inadequate.

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 a single, efficient sentence that front-loads the core purpose. However, it could be more structured by separating the API requirement into a second sentence for clarity.

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 (financial withdrawal operation), no annotations, 0% schema coverage, and no output schema, the description is incomplete. It misses parameter explanations, behavioral context (e.g., irreversibility), and expected outcomes. The private API note is insufficient for safe usage.

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%, so the description must compensate. It provides no information about any of the 6 parameters (currency, amount, address, net_type, secondary_address, transaction_type), their meanings, formats, or constraints. This leaves parameters completely undocumented.

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 as 'Request a digital asset withdrawal' with a specific verb ('Request') and resource ('digital asset withdrawal'), distinguishing it from siblings like CREATE_DEPOSIT_ADDRESS or GET_WITHDRAWAL. However, it doesn't explicitly differentiate from CANCEL_WITHDRAWAL in terms of action direction.

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 mentions 'requires private API', which implies a prerequisite but doesn't provide explicit guidance on when to use this tool versus alternatives like LIST_WITHDRAWALS or GET_WITHDRAWAL. No context on when-not-to-use or specific scenarios is provided.

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