Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_ACCOUNTS

Retrieve your Upbit cryptocurrency exchange account balances and asset information. This tool requires private API access to securely fetch your portfolio data.

Instructions

Get Upbit account balances (requires private API enabled)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function that implements the core logic of the GET_ACCOUNTS tool: authenticates via JWT, calls Upbit /accounts API, and returns formatted account balances.
    execute: async () => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const token = signJwtToken();
    	const data = await fetchJson<unknown>(client, "/accounts", {
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod input schema for the GET_ACCOUNTS tool, defining no required parameters.
    parameters: z.object({}),
  • src/index.ts:34-34 (registration)
    Registers the getAccountsTool with the FastMCP server instance.
    server.addTool(getAccountsTool);
Behavior3/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 of behavioral disclosure. It adds value by mentioning the authentication requirement ('requires private API enabled'), which is crucial context. However, it lacks details on rate limits, error handling, or what the return format looks like (e.g., balance structure), leaving gaps in behavioral transparency.

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, efficient sentence that front-loads the key information: the action and the prerequisite. There is no wasted text, and it's appropriately sized for a tool with no parameters and a straightforward purpose.

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?

Given the tool has no parameters, no annotations, and no output schema, the description is minimal but covers the core purpose and a key prerequisite. However, it lacks details on output format (e.g., what balances are returned, in what structure) and other behavioral aspects like error cases, making it incomplete for full agent understanding in a financial context.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is given since no parameters exist, and the description doesn't introduce confusion.

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 states the verb ('Get') and resource ('Upbit account balances'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like GET_DEPOSIT or GET_WITHDRAWAL, which also retrieve financial information, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by stating 'requires private API enabled', which indicates a prerequisite for usage. This helps the agent understand when this tool is applicable. However, it doesn't specify when to use this tool versus alternatives like GET_DEPOSIT or GET_WITHDRAWAL, or any exclusions, so it's not a perfect 5.

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