Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_ORDERS

Retrieve your Upbit cryptocurrency exchange order history and current status using private API access. Filter orders by market, state (wait/done/cancel), and paginate results.

Instructions

List Upbit orders (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNo
stateNowait
pageNo
limitNo

Implementation Reference

  • The main handler function that executes the tool: authenticates, builds query for Upbit orders API, fetches and returns JSON data.
    execute: async ({ market, state, page, limit }: Params) => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const query: Record<string, string> = {
    		state,
    		page: String(page),
    		limit: String(limit),
    	};
    	if (market) query.market = market;
    	const token = signJwtToken(query);
    	const data = await fetchJson<unknown>(client, "/orders", {
    		params: query,
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod schema defining input parameters for the tool: market (optional), state (wait/done/cancel), page, limit.
    const paramsSchema = z.object({
    	market: z.string().optional(),
    	state: z.enum(["wait", "done", "cancel"]).default("wait"),
    	page: z.number().int().min(1).default(1),
    	limit: z.number().int().min(1).max(100).default(100),
    });
  • src/index.ts:36-36 (registration)
    Registers the getOrdersTool (named GET_ORDERS) with the FastMCP server.
    server.addTool(getOrdersTool);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by noting the private API requirement, but it doesn't describe key behaviors such as pagination handling (implied by 'page' and 'limit' parameters), rate limits, error conditions, or what the output looks like (e.g., list format, fields). This leaves significant gaps for a tool with multiple parameters.

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 extremely concise—a single sentence that front-loads the core action ('List Upbit orders') and includes a critical note ('requires private API'). There's no wasted text, making it efficient and easy to parse.

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 tool's complexity (4 parameters, no output schema, and no annotations), the description is incomplete. It lacks details on parameter usage, output format, behavioral traits like pagination or errors, and differentiation from siblings. The private API note is helpful but insufficient for full contextual understanding.

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%, so the description must compensate for undocumented parameters. It doesn't add any meaning beyond the schema—no explanation of what 'market', 'state', 'page', or 'limit' mean in context, their formats, or how they affect the listing. This fails to address the coverage gap adequately.

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 ('List') and resource ('Upbit orders'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like GET_ORDER (singular) or GET_TRADES, which might cause confusion about 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?

The description mentions 'requires private API,' which provides some context about authentication needs, but it doesn't offer guidance on when to use this tool versus alternatives like GET_ORDER (for a single order) or GET_TRADES (for completed trades). No explicit when/when-not instructions or sibling comparisons are included.

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