Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_DEPOSIT_ADDRESSES

Retrieve deposit addresses for all supported cryptocurrencies on Upbit exchange. Use this tool to access your wallet addresses for receiving digital assets.

Instructions

List deposit addresses for all currencies (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function that implements the LIST_DEPOSIT_ADDRESSES tool: ensures private API access, constructs HTTP client, signs JWT token, fetches deposit addresses from Upbit's /deposits/coin_addresses endpoint, and returns formatted JSON.
    execute: async () => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const token = signJwtToken();
    	const data = await fetchJson<unknown>(client, "/deposits/coin_addresses", {
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Input schema using Zod: empty object, indicating no parameters are required for this tool.
    parameters: z.object({}),
  • src/index.ts:47-47 (registration)
    Registers the listDepositAddressesTool with the FastMCP server instance.
    server.addTool(listDepositAddressesTool);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the authentication requirement ('requires private API'), which is valuable behavioral context. However, it lacks details on rate limits, pagination, return format, error conditions, or whether this is a read-only operation. For a list tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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

Conciseness5/5

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

The description is a single, efficient sentence that states the core purpose upfront and includes the essential constraint ('requires private API'). There is zero waste or redundancy, and it's appropriately sized for a simple list tool with no parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the what and a key constraint (private API), but lacks details on output format, error handling, or behavioral traits. For a list operation in a financial API context, more completeness would be helpful, though the low complexity keeps it from being severely inadequate.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (though empty). With no parameters, the baseline is 4. The description doesn't need to explain parameters, and it doesn't introduce any parameter-related confusion. It appropriately focuses on the tool's purpose rather than non-existent 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 the verb 'List' and resource 'deposit addresses for all currencies', making the purpose specific and understandable. It distinguishes from siblings like GET_DEPOSIT_ADDRESS (singular) and LIST_DEPOSITS (deposits vs. addresses). However, it doesn't explicitly contrast with LIST_WITHDRAWAL_ADDRESSES, which is a similar list operation for a different resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context with 'requires private API', suggesting this tool is for authenticated users with specific permissions. However, it provides no explicit guidance on when to use this versus alternatives like GET_DEPOSIT_ADDRESS (for a single address) or how it relates to CREATE_DEPOSIT_ADDRESS. The usage is implied but not fully articulated.

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