Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_WITHDRAWALS

Retrieve withdrawal history from Upbit cryptocurrency exchange to track transaction status, view currency details, and monitor account activity using paginated results.

Instructions

List withdrawals (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNo
stateNo
pageNo
limitNo

Implementation Reference

  • The execute function that implements the LIST_WITHDRAWALS tool logic, authenticating and fetching withdrawal data from Upbit API.
    execute: async ({ currency, state, page, limit }: Params) => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const query = {
    		page,
    		limit,
    		currency,
    		state,
    	};
    	const token = signJwtToken(query);
    	const data = await fetchJson<unknown>(client, "/withdraws", {
    		params: query,
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod schema defining input parameters for the LIST_WITHDRAWALS tool: currency, state, page, and limit.
    const paramsSchema = z
    	.object({
    		currency: z.string().optional(),
    		state: z.string().optional(),
    		page: z.number().int().min(1).default(1),
    		limit: z.number().int().min(1).max(100).default(50),
    	})
    	.strict();
  • src/index.ts:42-42 (registration)
    Registers the listWithdrawalsTool with the FastMCP server.
    server.addTool(listWithdrawalsTool);
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 adds 'requires private API', which indicates authentication requirements, but lacks details on rate limits, pagination behavior (implied by 'page' and 'limit' params), error handling, or what 'list' entails (e.g., returns all withdrawals or a subset). This leaves significant behavioral gaps for a tool with multiple parameters.

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 front-loaded with the core purpose, but the parenthetical 'requires private API' adds necessary context without verbosity. It could be more structured by explicitly mentioning filtering or pagination, but it avoids unnecessary elaboration, earning a high score for efficiency.

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 complexity (4 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It lacks parameter explanations, behavioral details (e.g., pagination, authentication specifics), and output information, making it inadequate for effective tool selection and invocation in this 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 the description must compensate. It mentions no parameters, failing to explain the meaning of 'currency', 'state', 'page', or 'limit'. Without this, users cannot understand how to filter or paginate withdrawals, making the tool difficult to use correctly despite having 4 parameters.

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

Purpose3/5

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

The description 'List withdrawals (requires private API)' states the verb ('List') and resource ('withdrawals'), which gives a basic purpose. However, it's vague about scope (e.g., all withdrawals vs. filtered) and doesn't distinguish from sibling tools like GET_WITHDRAWAL or LIST_WITHDRAWAL_ADDRESSES, leaving room for confusion.

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 no guidance on when to use this tool versus alternatives. It mentions 'requires private API', which hints at authentication needs but doesn't specify when to choose LIST_WITHDRAWALS over GET_WITHDRAWAL or other withdrawal-related tools, offering no explicit usage context or exclusions.

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