Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_WITHDRAWAL_ADDRESSES

List all withdrawal addresses registered on your Upbit account. Requires private API access.

Instructions

List registered withdrawal-allowed addresses (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function that calls the Upbit API /withdraws/coin_addresses endpoint to list withdrawal-allowed addresses. It ensures private API is enabled, signs a JWT token, and fetches the data.
    export const listWithdrawalAddressesTool = {
    	name: "LIST_WITHDRAWAL_ADDRESSES",
    	description:
    		"List registered withdrawal-allowed addresses (requires private API)",
    	parameters: z.object({}),
    	execute: async () => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const token = signJwtToken();
    		const data = await fetchJson<unknown>(client, "/withdraws/coin_addresses", {
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Empty Zod schema (z.object({})) — no parameters are required for this tool.
    parameters: z.object({}),
  • src/index.ts:39-39 (registration)
    Registration of listWithdrawalAddressesTool with the FastMCP server via server.addTool().
    server.addTool(listWithdrawalAddressesTool);
  • src/index.ts:20-20 (registration)
    Import of listWithdrawalAddressesTool from the tool implementation file.
    import { listWithdrawalAddressesTool } from "./tools/list-withdrawal-addresses.js";
  • ensurePrivateEnabled() — validates that private API access is configured before the tool executes.
    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?

No annotations exist, so the description carries full burden. It only discloses the authentication requirement ('private API'), but fails to mention other behavioral traits such as idempotency, rate limits, or whether the list is exhaustive or paginated. This is insufficient for a tool with zero annotations.

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 sentence of 8 words, front-loading the action and resource. Every word is necessary and there is no redundancy or filler.

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 absence of annotations and output schema, the description should provide more context about the return value (e.g., list of addresses with fields) and any ordering or filtering. The tool is simple (no params), but the description is too sparse for an agent to understand what the output contains.

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 no parameters, and the schema coverage is 100% by default. The description does not add parameter-specific information, but none is needed. The baseline for zero parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List'), the resource ('registered withdrawal-allowed addresses'), and distinguishes from sibling LIST_WITHDRAWALS which lists withdrawals, not addresses. The tool name is self-explanatory and the description adds clarity about the scope.

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 mentions 'requires private API', implying it's for authenticated users only, but does not explicitly state when to use this tool versus alternatives like LIST_DEPOSIT_ADDRESSES or LIST_WITHDRAWALS. The differentiation is based on the resource name, but no direct guidance on selection criteria is provided.

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