Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_TICKER

Retrieve current ticker data for a specific market from Upbit. Input the market code (e.g., KRW-BTC) to get real-time price, volume, and change information.

Instructions

Get the latest ticker data from Upbit for a single market

Input Schema

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

Implementation Reference

  • The getTickerTool object containing the name 'GET_TICKER', description, parameters schema, and the execute async function that fetches ticker data from Upbit API and returns it as a JSON string.
    export const getTickerTool = {
    	name: "GET_TICKER",
    	description: "Get the latest ticker data from Upbit for a single market",
    	parameters: paramsSchema,
    	execute: async ({ market }: Params) => {
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const data = await fetchJson<unknown>(client, "/ticker", {
    			params: { markets: market },
    		});
    		const item = Array.isArray(data) ? (data as any[])[0] : (data as any);
    		return JSON.stringify(item, null, 2);
    	},
    } as const;
  • Zod schema for the 'market' parameter (string min 3 chars, describes Upbit market code e.g., KRW-BTC).
    const paramsSchema = z.object({
    	market: z.string().min(3).describe("Upbit market code, e.g., KRW-BTC"),
    });
  • src/index.ts:15-15 (registration)
    Import of getTickerTool from the get-ticker module.
    import { getTickerTool } from "./tools/get-ticker.js";
  • src/index.ts:31-31 (registration)
    Registration of getTickerTool on the FastMCP server via server.addTool().
    server.addTool(getTickerTool);
  • The fetchJson helper function used by the getTickerTool execute handler to make HTTP GET requests to the Upbit API.
    export async function fetchJson<T>(
    	client: AxiosInstance,
    	url: string,
    	options: {
    		method?: "GET" | "POST" | "DELETE" | "PUT" | "PATCH";
    		params?: Record<string, unknown>;
    		data?: unknown;
    		headers?: Record<string, string>;
    	} = {},
    	schema?: z.ZodType<T>,
    ): Promise<T> {
    	try {
    		const response = await client.request({
    			url,
    			method: options.method ?? "GET",
    			params: options.params,
    			data: options.data,
    			headers: options.headers,
    		});
    
    		const data = response.data;
    		if (schema) {
    			return schema.parse(data);
    		}
    		return data as T;
    	} catch (err) {
    		if (axios.isAxiosError(err)) {
    			const ae = err as AxiosError;
    			const status = ae.response?.status ?? 0;
    			const message = ae.message || "HTTP request failed";
    			const data = ae.response?.data;
    			throw new HttpError(status, message, data);
    		}
    		throw err;
    	}
    }
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. It simply says 'Get' without clarifying that it is a read-only, non-destructive operation. No mention of rate limits, data freshness, or other behavioral traits.

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?

A single, clear sentence that is front-loaded and contains no extraneous words. Every word earns its place.

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 no output schema and no annotations, the description is minimal. It does not describe return values (e.g., price, volume) or pagination behavior, but the tool name and standard ticker format partly compensate. Adequate but could be more informative.

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?

Schema description coverage is 100%, with the 'market' parameter already documented with an example. The description reinforces 'for a single market' but adds no new semantic detail beyond the schema. Baseline of 3 applies.

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 states 'Get the latest ticker data from Upbit for a single market', clearly identifying the verb (get), resource (ticker data), and scope (single market). It is distinct from siblings like GET_ORDERBOOK or GET_TRADES, though it could be more explicit about what 'ticker data' includes.

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 on when to use this tool versus alternatives (e.g., for multiple markets you would need multiple calls). No exclusions or context provided about prerequisites or suitable scenarios.

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