Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

GET_TRADES

Retrieve recent cryptocurrency trade data from Upbit exchange to analyze market activity and transaction patterns for informed trading decisions.

Instructions

Get recent trades for a market

Input Schema

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

Implementation Reference

  • The main handler function that executes the tool logic: fetches recent trades from Upbit API for the given market and returns formatted JSON.
    execute: async ({ market }: Params) => {
    	const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    	const client = createHttpClient(baseURL);
    	const data = await fetchJson<unknown>(client, "/trades/ticks", {
    		params: { market },
    	});
    	return JSON.stringify(data, null, 2);
    },
  • Zod schema defining the input parameter 'market' for the tool.
    const paramsSchema = z.object({
    	market: z.string().min(3).describe("Upbit market code, e.g., KRW-BTC"),
    });
  • src/index.ts:33-33 (registration)
    Registers the getTradesTool with the FastMCP server.
    server.addTool(getTradesTool);
  • src/index.ts:16-16 (registration)
    Imports the getTradesTool from its definition file.
    import { getTradesTool } from "./tools/get-trades.js";
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 the basic action. It does not disclose behavioral traits like rate limits, authentication needs, pagination, or what 'recent' means (e.g., time range, limit), leaving significant gaps for an agent to understand how to use it effectively.

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, clear sentence with no wasted words, making it appropriately sized and front-loaded. It efficiently conveys the core purpose without unnecessary elaboration.

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 (a read operation with no annotations and no output schema), the description is incomplete. It lacks details on return values, error handling, or behavioral context, making it insufficient for an agent to fully understand the tool's operation and outcomes.

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 semantics beyond the input schema, which has 100% coverage and fully describes the 'market' parameter. Since schema coverage is high, the baseline is 3, as the description does not compensate with additional details like format examples or constraints.

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 action ('Get') and resource ('recent trades for a market'), making the purpose understandable. However, it does not differentiate from sibling tools like GET_ORDERBOOK or GET_TICKER, which also retrieve market data, so it lacks sibling distinction.

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 such as GET_ORDERBOOK or GET_TICKER, nor does it mention any prerequisites or exclusions. It only states what the tool does without context for selection.

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