Skip to main content
Glama
solangii

Upbit MCP Server

get_trades

Retrieve recent trade ticks for a specific cryptocurrency symbol from Upbit exchange to analyze market activity and trading patterns.

Instructions

Get recent trade ticks for a symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • The main handler function that implements the get_trades tool logic: fetches recent trade ticks for a symbol from the Upbit API endpoint.
    async def get_trades(symbol: str) -> list[dict]:
        """Get recent trade ticks for a symbol"""
        url = f"{API_BASE}/trades/ticks"
        async with httpx.AsyncClient() as client:
            res = await client.get(url, params={"market": symbol})
            return res.json()
  • main.py:44-44 (registration)
    Registers the get_trades function as an MCP tool using FastMCP's tool decorator.
    mcp.tool()(get_trades)
  • main.py:8-8 (registration)
    Imports the get_trades handler function for use in registration.
    from tools.get_trades import get_trades
Behavior2/5

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

With no annotations, the description carries full burden but only states basic functionality. It doesn't disclose behavioral traits like rate limits, authentication needs, pagination, or what 'recent' means (e.g., time window). This leaves significant gaps for a tool that likely returns time-sensitive 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 with zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 (likely returning time-series trade data), no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on return format (e.g., list of ticks with timestamps), error handling, or prerequisites, making it insufficient for effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds minimal meaning. It mentions 'symbol' as the parameter but doesn't explain format (e.g., trading pair like BTC-USD) or constraints. This is inadequate for a single required parameter with no schema documentation.

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

Purpose3/5

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

The description 'Get recent trade ticks for a symbol' clearly states the verb ('Get') and resource ('recent trade ticks'), but it's vague about scope (e.g., time range, limit) and doesn't distinguish from siblings like get_orderbook or get_ticker. It avoids tautology but lacks specificity.

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 is provided on when to use this tool versus alternatives such as get_orderbook (for market depth) or get_ticker (for price summaries). The description implies usage for trade history but offers no explicit context or exclusions.

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/solangii/upbit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server