Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

CREATE_DEPOSIT_ADDRESS

Generate a deposit address on Upbit exchange to receive cryptocurrency deposits for a specified currency and network type.

Instructions

Request creation of a deposit address (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
net_typeYes

Implementation Reference

  • Handler function that authenticates and makes a POST request to Upbit API to create a deposit address.
    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);
    },
  • Zod schema defining input parameters: currency (string) and net_type (string).
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		net_type: z.string(),
    	})
    	.strict();
  • src/index.ts:45-45 (registration)
    Registration of the createDepositAddressTool in the FastMCP server.
    server.addTool(createDepositAddressTool);
Behavior2/5

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

With no annotations provided, the description carries full burden but only mentions 'requires private API' for authentication. It fails to disclose critical behavioral traits like whether this is a read/write operation, potential side effects (e.g., creating a new address in a database), rate limits, or error conditions, 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.

Conciseness4/5

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

The description is brief and to the point with a single sentence, avoiding unnecessary details. However, it could be more front-loaded by immediately stating the core action without the parenthetical note, though it remains efficient overall.

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 tool's complexity (creation operation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It misses key details like parameter meanings, behavioral implications, and expected outputs, making it inadequate for safe and effective use by an AI agent.

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

Parameters2/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 but adds no information about the two required parameters (currency, net_type). It doesn't explain what these parameters mean, their expected values, or how they affect the deposit address creation, resulting in poor parameter guidance.

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 action ('Request creation') and resource ('deposit address'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like GET_DEPOSIT_ADDRESS or LIST_DEPOSIT_ADDRESSES, which would require explicit differentiation to achieve a perfect score.

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 provides minimal guidance with 'requires private API', hinting at authentication needs, but lacks explicit when-to-use instructions, alternatives (e.g., vs. GET_DEPOSIT_ADDRESS), or prerequisites beyond API access. This leaves usage context vague and incomplete.

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