Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_ORDER

Retrieve a specific order from the Upbit cryptocurrency exchange using its unique identifier or UUID. This tool accesses private API data to provide detailed order information for tracking and analysis.

Instructions

Get a single Upbit order (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNo
identifierNo

Implementation Reference

  • The execute function that implements the core logic of the GET_ORDER tool, authenticating and fetching a single order from the Upbit API using either UUID or identifier.
    execute: async ({ uuid, identifier }: Params) => {
    	ensurePrivateEnabled();
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const query: Record<string, string> = {};
    	if (uuid) query.uuid = uuid;
    	if (identifier) query.identifier = identifier;
    	const token = signJwtToken(query);
    	const data = await fetchJson<unknown>(client, "/order", {
    		params: query,
    		headers: { Authorization: `Bearer ${token}` },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod schema defining the input parameters for the GET_ORDER tool: optional uuid or identifier (at least one required).
    const paramsSchema = z
    	.object({
    		uuid: z.string().optional(),
    		identifier: z.string().optional(),
    	})
    	.refine((v) => v.uuid || v.identifier, {
    		message: "Either uuid or identifier is required",
    	});
  • src/index.ts:37-37 (registration)
    Registers the getOrderTool (named GET_ORDER) with the FastMCP server.
    server.addTool(getOrderTool);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'requires private API', which hints at authentication needs, but doesn't cover other critical aspects like rate limits, error conditions, response format, or whether this is a read-only operation (implied by 'Get' but not explicit). The description is too sparse for a tool that likely involves sensitive financial data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and to the point with a single sentence, making it easy to parse. However, it could be more front-loaded by immediately stating the core purpose before the API requirement, and the lack of parameter information means it's somewhat under-specified rather than optimally concise.

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 complexity of a financial API tool with no annotations, no output schema, and 2 undocumented parameters, the description is incomplete. It misses critical details like parameter meanings, authentication specifics, error handling, and response structure, making it inadequate for safe and effective use by an AI agent.

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?

The description provides no information about the two parameters (uuid and identifier), and schema description coverage is 0%. This leaves parameters completely undocumented, with no explanation of what they represent, their relationship, or whether one is required over the other.

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 ('a single Upbit order'), making the purpose specific and understandable. It distinguishes from sibling tools like GET_ORDERS (plural) by specifying 'single', but doesn't explicitly contrast with other tools like GET_ACCOUNTS or GET_TICKER beyond the resource type.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'requires private API', which is a prerequisite rather than usage context, and doesn't explain when to choose GET_ORDER over GET_ORDERS or other sibling tools for order-related queries.

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