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 to receive funds.

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 that makes an HTTP request to GET /deposits/coin_address with the currency and net_type parameters. It signs a JWT token for authentication and returns the deposit address data.
    export const getDepositAddressTool = {
    	name: "GET_DEPOSIT_ADDRESS",
    	description:
    		"Get a single deposit address for a currency and net_type (private)",
    	parameters: paramsSchema,
    	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);
    	},
    } as const;
  • Zod schema defining the input parameters: currency (string) and net_type (string), using .strict() to reject unknown fields.
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		net_type: z.string(),
    	})
    	.strict();
  • src/index.ts:46-46 (registration)
    Registration of the tool with the FastMCP server via server.addTool(getDepositAddressTool) on line 46.
    server.addTool(getDepositAddressTool);
  • src/index.ts:10-10 (registration)
    Import statement for the getDepositAddressTool from the tools module.
    import { getDepositAddressTool } from "./tools/get-deposit-address.js";
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the obvious read operation. The parenthetical '(private)' is ambiguous and does not clarify side effects, permissions, or rate limits.

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

Conciseness3/5

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

The description is very concise at one sentence, which is efficient. However, it sacrifices clarity for brevity, missing opportunities to front-load key usage details.

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, the description should indicate what the tool returns (e.g., an address string). It also lacks context on how this fits with siblings like GET_DEPOSIT or GET_ACCOUNTS, making the tool less discoverable.

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?

The description mentions 'currency' and 'net_type (private)' but provides no additional meaning beyond the schema names. With 0% schema coverage, the description fails to explain valid values or formats, leaving the agent to guess.

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 'Get a single deposit address' with specific parameters 'currency and net_type'. This distinguishes it from LIST_DEPOSIT_ADDRESSES which lists multiple addresses. However, it does not explain what a deposit address is, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives like CREATE_DEPOSIT_ADDRESS or LIST_DEPOSIT_ADDRESSES. The context of 'private' net_type is unclear, and there is no mention of prerequisites or when to prefer this over other tools.

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