Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

CREATE_WITHDRAWAL

Initiate a digital asset withdrawal by specifying currency, amount, recipient address, and network type.

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 execute function that performs the withdrawal request. It validates private API access is enabled, constructs the HTTP client, signs a JWT token with the request params, and POSTs to /withdraws/coin on Upbit's 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 validation schema for CREATE_WITHDRAWAL parameters: currency (string), amount (string), address (string), net_type (string), optional secondary_address, and optional transaction_type (default or internal).
    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:7-7 (registration)
    Import of the createWithdrawalTool from the tool module.
    import { createWithdrawalTool } from "./tools/create-withdrawal.js";
  • src/index.ts:40-40 (registration)
    Registration of the CREATE_WITHDRAWAL tool with the FastMCP server via server.addTool().
    server.addTool(createWithdrawalTool);
  • ensurePrivateEnabled() - helper that validates private API credentials are configured before proceeding with the withdrawal.
    export function ensurePrivateEnabled(): void {
    	if (!config.upbit.enablePrivate) {
    		throw new Error(
    			"Private trading tools are disabled. Set UPBIT_ENABLE_TRADING=true to enable.",
    		);
    	}
    	if (!config.upbit.accessKey || !config.upbit.secretKey) {
    		throw new Error(
    			"Upbit API keys are not configured. Set UPBIT_ACCESS_KEY and UPBIT_SECRET_KEY.",
    		);
    	}
    }
Behavior2/5

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

The only behavioral note is 'requires private API', which is authentication-related. It does not disclose that the withdrawal is destructive (funds moved), irreversible, or requires confirmations. Annotations are absent, so the description fails to provide critical safety information.

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

Conciseness2/5

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

The description is a single sentence, but it is under-specified rather than concise. It omits essential details, so brevity comes at the expense of usefulness. The structure provides no front-loaded key points beyond the title.

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?

Given 6 parameters, no output schema, no annotations, and siblings handling withdrawal lifecycle, the description is grossly incomplete. It does not mention success/error responses, processing time, or constraints. An agent cannot reliably invoke this tool.

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 coverage is 0%, and the description adds no parameter explanations. With 6 parameters (4 required), an agent needs semantics for currency, amount, address, net_type, etc. The description is entirely silent, making parameter invocation guesswork.

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

Purpose3/5

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

The description identifies the action as requesting a withdrawal, but is vague. It does not specify the type of digital asset or the context beyond 'requires private API', which is more authentication info than purpose. It avoids tautology but lacks specificity.

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?

No guidance on when to use this tool versus siblings like CANCEL_WITHDRAWAL. The description mentions 'requires private API' but does not clarify prerequisites or scenarios. An agent has no context to decide between alternatives.

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