Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_DEPOSIT

Retrieve a specific deposit record from your Upbit account using its unique UUID. Requires private API access.

Instructions

Get a single deposit by UUID (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Implementation Reference

  • The handler/execute function for GET_DEPOSIT tool. Calls the Upbit /deposit API with a JWT-signed query containing the deposit UUID, and returns the response as JSON.
    export const getDepositTool = {
    	name: "GET_DEPOSIT",
    	description: "Get a single deposit by UUID (requires private API)",
    	parameters: paramsSchema,
    	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, "/deposit", {
    			params: query,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema defining the required input parameter: a non-empty string 'uuid'.
    const paramsSchema = z.object({ uuid: z.string().min(1) });
  • src/index.ts:48-48 (registration)
    Registration of the getDepositTool on the FastMCP server instance.
    server.addTool(getDepositTool);
  • src/index.ts:9-9 (registration)
    Import of the getDepositTool from the get-deposit module into the main server entry point.
    import { getDepositTool } from "./tools/get-deposit.js";
  • Imports for helper utilities: ensurePrivateEnabled checks private API access is configured, signJwtToken signs the query parameters for authenticated requests.
    import { ensurePrivateEnabled, signJwtToken } from "../lib/upbit-auth.js";
Behavior3/5

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

No annotations provided. Description states it requires private API (auth needed), but does not explicitly confirm read-only nature or mention any side effects, rate limits, or pitfalls. 'Get' implies read but could be more explicit.

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?

Single sentence conveys essential purpose and access requirement with zero wasted words. Optimal conciseness for a simple retrieval tool.

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?

Adequate for a simple single-resource retrieval, but missing output schema and description does not hint at return structure. Agent may need to infer response contains deposit details. Fairly complete given low complexity.

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 has 0% description coverage for the uuid parameter. Description adds 'by UUID' which is already clear from name. No additional semantics like format, example, or special constraints beyond minLength.

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?

Description clearly states action (Get), object (deposit), and identifier (UUID). Distinguishes from sibling LIST_DEPOSITS (list) and GET_DEPOSIT_ADDRESS (address). Mention of 'requires private API' adds important context.

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?

Implies usage when a single deposit UUID is available, but provides no explicit guidance on when to use this vs alternatives like GET_DEPOSIT_CHANCE or LIST_DEPOSITS. No exclusions or higher-level context given.

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