Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

CREATE_DEPOSIT_ADDRESS

Generate a cryptocurrency deposit address by specifying the currency and network type through your Upbit private API.

Instructions

Request creation of a deposit address (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
net_typeYes

Implementation Reference

  • The execute function that handles the CREATE_DEPOSIT_ADDRESS tool: ensures private API is enabled, signs a JWT token with the params, and POSTs to /deposits/coin_address to request creation of a deposit address.
    export const createDepositAddressTool = {
    	name: "CREATE_DEPOSIT_ADDRESS",
    	description: "Request creation of a deposit address (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, "/deposits/coin_address", {
    			method: "POST",
    			data: params,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema defining input parameters: currency (string) and net_type (string), strict mode enabled.
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		net_type: z.string(),
    	})
    	.strict();
  • src/index.ts:45-45 (registration)
    Registration of the createDepositAddressTool via server.addTool() in the main function.
    server.addTool(createDepositAddressTool);
  • signJwtToken helper: creates a JWT with access_key, nonce, and a SHA-512 hash of sorted query params.
    export function signJwtToken(
    	params?: Record<string, string | number | boolean | undefined>,
    ): string {
    	const payload: Record<string, unknown> = {
    		access_key: config.upbit.accessKey,
    		nonce: crypto.randomUUID(),
    	};
    
    	if (params && Object.keys(params).length > 0) {
    		const searchParams = new URLSearchParams();
    		const sortedKeys = Object.keys(params).sort();
    		for (const key of sortedKeys) {
    			const value = params[key];
    			if (value === undefined) continue;
    			searchParams.append(key, String(value));
    		}
    		const encoded = searchParams.toString();
    		const queryHash = crypto.createHash("sha512").update(encoded).digest("hex");
    		payload.query_hash = queryHash;
    		payload.query_hash_alg = "SHA512";
    	}
    
    	return jwt.sign(payload, config.upbit.secretKey as string);
    }
  • ensurePrivateEnabled helper: validates that private API trading is enabled and API keys are configured.
    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?

With no annotations, the description carries the full burden for behavioral traits. It states the tool is a creation action requiring private API, but fails to disclose potential side effects (e.g., whether it overwrites existing addresses), rate limits, or what happens on failure. This is insufficient for safe agent invocation.

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 concise sentence of 8 words, front-loading the core action. While efficient, it sacrifices necessary detail; a slightly longer description would improve completeness without sacrificing conciseness.

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 no output schema and no annotations, the description fails to provide adequate context. It does not explain the return value, error conditions, or any constraints beyond the private API requirement. The two parameters are also left undocumented, making the tool under-specified.

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%, meaning the input schema provides no parameter descriptions. The tool description does not compensate: it omits any explanation of the 'currency' and 'net_type' parameters, such as allowed values, formats, or examples. This leaves the agent unable to construct valid inputs.

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 it requests creation of a deposit address, matching the verb and resource. It distinguishes itself from sibling tools like GET_DEPOSIT_ADDRESS and LIST_DEPOSIT_ADDRESSES by indicating it creates rather than retrieves. However, it could be more explicit about its specific role in the deposit workflow.

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 notes 'requires private API' but provides no guidance on when to use this tool versus alternatives like GET_DEPOSIT_ADDRESS or LIST_DEPOSIT_ADDRESSES. There is no mention of prerequisites, limitations, or when not to use it, leaving the agent without context for selection.

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