Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_DEPOSIT_ADDRESS

Retrieve a deposit address for a specific cryptocurrency and network type on the Upbit exchange to enable fund transfers.

Instructions

Get a single deposit address for a currency and net_type (private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
net_typeYes

Implementation Reference

  • The execute function implementing the core logic of the GET_DEPOSIT_ADDRESS tool: authenticates and fetches deposit address from Upbit API.
    execute: async ({ currency, net_type }: Params) => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const query = { currency, net_type };
    	const token = signJwtToken(query);
    	const data = await fetchJson<unknown>(client, "/deposits/coin_address", {
    		params: query,
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod schema defining input parameters for the tool: currency (string) and net_type (string).
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		net_type: z.string(),
    	})
    	.strict();
  • src/index.ts:46-46 (registration)
    Registers the getDepositAddressTool with the FastMCP server.
    server.addTool(getDepositAddressTool);
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 offers minimal behavioral insight. It mentions the tool is for 'private' net_type, hinting at access control, but doesn't disclose permissions needed, rate limits, idempotency, or what happens if no address exists. More context is needed for a mutation-sensitive domain.

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 usage notes or parameter details, but given its brevity, it avoids unnecessary fluff.

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?

For a tool with 2 required parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain return values, error handling, or operational constraints, leaving significant gaps for an AI agent to invoke it correctly in a financial context.

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 parameters are undocumented in the schema. The description adds minimal semantics by naming 'currency' and 'net_type' but provides no format, examples, or constraints (e.g., valid currencies, net_type values like 'mainnet'). It doesn't compensate for the coverage gap.

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 ('Get') and resource ('a single deposit address'), specifying it's for a currency and net_type. It distinguishes from sibling LIST_DEPOSIT_ADDRESSES by emphasizing 'single' vs. 'list', but doesn't explicitly contrast with CREATE_DEPOSIT_ADDRESS (which likely creates new addresses).

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 explicit guidance on when to use this tool versus alternatives like LIST_DEPOSIT_ADDRESSES or CREATE_DEPOSIT_ADDRESS. The description implies usage for retrieving an existing address, but lacks context on prerequisites, error conditions, or typical scenarios.

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