Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_DEPOSITS

List deposit transactions with optional filtering by currency, state, and pagination using your private Upbit API.

Instructions

List deposits (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNo
stateNo
pageNo
limitNo

Implementation Reference

  • Main tool handler: executes the LIST_DEPOSITS tool logic. Validates params via Zod schema, checks private API is enabled, builds query params, signs a JWT token for Upbit API auth, calls GET /deposits, and returns JSON-stringified response.
    export const listDepositsTool = {
    	name: "LIST_DEPOSITS",
    	description: "List deposits (requires private API)",
    	parameters: paramsSchema,
    	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, "/deposits", {
    			params: query,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod paramsSchema defining input validation for LIST_DEPOSITS: optional currency (string), optional state (string), page (int >=1, default 1), limit (int 1-100, default 50). Strict mode rejects unknown keys.
    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:49-49 (registration)
    Registration via server.addTool(listDepositsTool) in the main FastMCP server setup.
    server.addTool(listDepositsTool);
  • src/index.ts:19-19 (registration)
    Import statement for listDepositsTool from the list-deposits.ts module.
    import { listDepositsTool } from "./tools/list-deposits.js";
  • Helper ensurePrivateEnabled() called by the handler to check that private API trading is enabled and API keys are configured before making the request.
    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?

With no annotations, the description must convey behavioral traits. It mentions 'requires private API' (authentication), but omits whether the operation is read-only, pagination behavior, rate limits, or side effects.

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 short and front-loaded, but the extreme brevity sacrifices essential details, making it incomplete rather than concise.

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

Completeness1/5

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

Given 0% schema coverage, no output schema, and 4 parameters, the description is grossly insufficient. It does not explain what deposits are listed, filtering, pagination, or output structure.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description provides no explanation for the 4 parameters (currency, state, page, limit). The agent cannot infer valid values or usage patterns.

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 states the action (list) and resource (deposits) clearly. However, it lacks differentiation from sibling tools like GET_DEPOSIT or LIST_WITHDRAWALS, leaving ambiguity about the tool's specific scope.

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 on when to use this tool versus alternatives. The only context is 'requires private API,' which hints at authorization but does not explain conditions for use or provide examples.

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