Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_WITHDRAWAL

Retrieve details of a single withdrawal using its unique UUID. Requires private API access for secure retrieval.

Instructions

Get a single withdrawal by UUID (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Implementation Reference

  • The execute handler function that makes the authenticated GET /withdraw API call with a uuid parameter.
    	execute: async ({ uuid }: Params) => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const query = { uuid };
    		const token = signJwtToken(query);
    		const data = await fetchJson<unknown>(client, "/withdraw", {
    			params: query,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema defining the required 'uuid' string parameter.
    const paramsSchema = z.object({ uuid: z.string().min(1) });
  • src/index.ts:41-41 (registration)
    Registration of the getWithdrawalTool on the MCP server via server.addTool(getWithdrawalTool).
    server.addTool(getWithdrawalTool);
  • src/index.ts:17-17 (registration)
    Import of getWithdrawalTool from the tools module.
    import { getWithdrawalTool } from "./tools/get-withdrawal.js";
  • Imports for config, HTTP client, and Upbit auth helpers (ensurePrivateEnabled, signJwtToken).
    import { z } from "zod";
    import { config } from "../lib/config.js";
    import { createHttpClient, fetchJson } from "../lib/http.js";
    import { ensurePrivateEnabled, signJwtToken } from "../lib/upbit-auth.js";
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only mentions 'requires private API' but does not disclose whether the operation is read-only, what happens on error (e.g., invalid UUID), or any rate limits. This is insufficient for a tool that likely queries sensitive data.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose and a key constraint (private API).

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 that retrieves a single withdrawal, the description lacks any hint about the return value or output structure. Without an output schema, the agent cannot infer what data will be provided. Error handling or prerequisite details are also missing, making the description incomplete for practical use.

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

Parameters3/5

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

The input schema has one parameter (uuid) with no description (0% coverage). The description mentions 'by UUID' but does not explain what constitutes a valid UUID or its format. Given the low schema coverage, the description partially compensates but adds limited semantic value.

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 ('Get'), the resource ('withdrawal'), and the identifier ('by UUID'). It also notes a requirement ('requires private API'). This distinguishes it from sibling tools like LIST_WITHDRAWALS and CREATE_WITHDRAWAL.

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 that the tool requires a private API, implying authentication context. However, it does not explicitly state when to use it versus alternatives (e.g., LIST_WITHDRAWALS for all withdrawals). The context from sibling names offers some guidance, but the description itself lacks explicit usage instructions.

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