Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_TICKER

Retrieve current market price and trading data for a specific cryptocurrency pair on Upbit exchange to monitor real-time market conditions.

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 execute function that handles the tool logic: fetches the latest ticker data from Upbit API for the given 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, "/ticker", {
    		params: { markets: market },
    	});
    	const item = Array.isArray(data) ? (data as any[])[0] : (data as any);
    	return JSON.stringify(item, null, 2);
    },
  • Zod schema defining the input parameter 'market' for the GET_TICKER tool.
    const paramsSchema = z.object({
    	market: z.string().min(3).describe("Upbit market code, e.g., KRW-BTC"),
    });
  • src/index.ts:31-31 (registration)
    Registers the getTickerTool with the FastMCP server.
    server.addTool(getTickerTool);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, rate limits, authentication needs, error conditions, or what data format is returned. This leaves significant behavioral gaps for an agent.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple data retrieval tool and is front-loaded with the essential information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'ticker data' includes (price, volume, etc.), return format, error handling, or API constraints. Given the lack of structured metadata, the description should provide more operational context.

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 description adds no parameter information beyond what's already in the schema (which has 100% coverage). It mentions 'single market' which aligns with the single 'market' parameter, but provides no additional context about market codes, examples beyond the schema's 'KRW-BTC', or parameter constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get'), resource ('latest ticker data'), and scope ('from Upbit for a single market'), distinguishing it from siblings like GET_ORDERBOOK or GET_TRADES by focusing on current market data rather than order or trade history.

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

Usage Guidelines3/5

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

The description implies usage for retrieving current market data, but provides no explicit guidance on when to use this tool versus alternatives like GET_ORDERBOOK (for order depth) or GET_TRADES (for recent trades). It lacks any 'when-not' or prerequisite information.

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