Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_ORDERBOOK

Retrieve real-time orderbook data for cryptocurrency markets on Upbit to analyze market depth and trading opportunities.

Instructions

Get orderbook snapshot for a given market

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesUpbit market code, e.g., KRW-BTC

Implementation Reference

  • The main handler function that performs an HTTP request to the Upbit API to fetch the orderbook for the specified market and returns it as formatted JSON.
    execute: async ({ market }: Params) => {
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const data = await fetchJson<unknown>(client, "/orderbook", {
    		params: { markets: market },
    	});
    	/** biome-ignore lint/suspicious/noExplicitAny: <not important> */
    	const item = Array.isArray(data) ? (data as any[])[0] : (data as any);
    	return JSON.stringify(item, null, 2);
    },
  • Zod schema defining the input parameters for the tool, specifically the 'market' string.
    const paramsSchema = z.object({
    	market: z.string().min(3).describe("Upbit market code, e.g., KRW-BTC"),
    });
  • src/index.ts:32-32 (registration)
    Registers the getOrderbookTool with the FastMCP server instance.
    server.addTool(getOrderbookTool);
Behavior2/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 mentions retrieving a 'snapshot', implying a read-only operation, but fails to detail aspects like rate limits, data freshness, error conditions, or response format. This leaves significant gaps for a tool that interacts with market data.

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 directly states the tool's purpose without any unnecessary words. It is front-loaded and appropriately sized for a simple tool, earning full marks for conciseness.

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's simplicity (one parameter, no output schema, no annotations), the description is minimally adequate but lacks depth. It explains what the tool does but omits important context like the structure of the orderbook snapshot, potential errors, or how it differs from other market data tools, leaving room for improvement.

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

Parameters3/5

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

The input schema has 100% description coverage, with the 'market' parameter well-documented as an Upbit market code. The description adds no additional semantic context beyond what the schema provides, such as example usage or constraints, so it meets the baseline for high schema coverage.

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 the resource 'orderbook snapshot for a given market', making the purpose specific and understandable. However, it does not distinguish this tool from potential siblings like GET_TICKER or GET_TRADES that also provide market data, which prevents a score of 5.

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 like GET_TICKER or GET_TRADES, nor does it mention prerequisites or exclusions. It only states what the tool does, leaving usage context implied at best.

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