Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_DEPOSIT_CHANCE

Verify deposit availability for a cryptocurrency on Upbit by specifying the currency and optional network type.

Instructions

Get deposit availability information for a currency (private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
net_typeNo

Implementation Reference

  • The main tool definition and execute handler for GET_DEPOSIT_CHANCE. It validates params, ensures private auth, builds a JWT token, and calls the Upbit /deposits/chance/coin API.
    export const getDepositChanceTool = {
    	name: "GET_DEPOSIT_CHANCE",
    	description: "Get deposit availability information for a currency (private)",
    	parameters: paramsSchema,
    	execute: async ({ currency, net_type }: Params) => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const query = { currency, net_type };
    		const token = signJwtToken(query);
    		const data = await fetchJson<unknown>(client, "/deposits/chance/coin", {
    			params: query,
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Zod schema defining input parameters: currency (required string) and net_type (optional string).
    const paramsSchema = z
    	.object({
    		currency: z.string(),
    		net_type: z.string().optional(),
    	})
    	.strict();
  • src/index.ts:44-44 (registration)
    Registration of getDepositChanceTool with the FastMCP server via server.addTool().
    server.addTool(getDepositChanceTool);
  • src/index.ts:11-11 (registration)
    Import of getDepositChanceTool from the get-deposit-chance module.
    import { getDepositChanceTool } from "./tools/get-deposit-chance.js";
  • Imports for config, HTTP client, and Upbit auth helpers (ensurePrivateEnabled, signJwtToken) used by the handler.
    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 exist, and the description does not disclose behavioral traits such as whether this is a read-only operation, required permissions, rate limits, or side effects. The term '(private)' hints at access restrictions but lacks clarity.

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 a single sentence that is front-loaded with the core action, but it is overly terse and sacrifices necessary detail. It earns its place but could be expanded without becoming verbose.

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 lack of output schema and annotations, the description fails to cover return values, error handling, or how 'availability information' is structured. Context with sibling tools is not leveraged to clarify usage.

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%, yet the description adds no explanation for the two parameters ('currency' and 'net_type'). It does not clarify their formats, allowed values, or purpose beyond what the schema fields imply.

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 clearly identifies the tool as retrieving deposit availability information for a currency, with the '(private)' qualifier. It specifies the resource ('deposit availability') and differentiates from other deposit tools like LIST_DEPOSITS or GET_DEPOSIT, though the term 'chance' remains somewhat ambiguous.

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 is provided on when to use this tool versus sibling tools like GET_DEPOSIT or LIST_DEPOSITS. The description lacks any context about prerequisites, alternatives, or conditions when this tool is appropriate.

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