Skip to main content
Glama
enesjakozh
solangii

Upbit MCP Server

by solangii
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_orderbook

Retrieve real-time orderbook data for cryptocurrency trading pairs on Upbit to analyze market depth and make informed trading decisions.

Instructions

Get orderbook snapshot for a given symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • tools/get_orderbook.py:4-9 (handler)
    The main handler function that fetches the orderbook snapshot for a given symbol using the Upbit API via httpx.
    async def get_orderbook(symbol: str) -> dict:
    """Get orderbook snapshot for a given symbol"""
    url = f"{API_BASE}/orderbook"
    async with httpx.AsyncClient() as client:
        res = await client.get(url, params={"markets": symbol})
        return res.json()[0]
  • main.py:43-43 (registration)
    Registers the imported get_orderbook function as an MCP tool using FastMCP's decorator.
    mcp.tool()(get_orderbook)

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'snapshot,' implying a read-only operation, but doesn't specify if it's real-time or cached, rate limits, authentication needs, or what the output format looks like. This leaves significant gaps for an agent to understand how to handle the tool's behavior.

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 function without any wasted words. It is 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 complexity of market data tools, no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on output format, behavioral traits like latency or limits, and differentiation from siblings, making it inadequate for reliable agent 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 for the undocumented parameter. It adds meaning by specifying that the 'symbol' parameter is used to identify the market for the orderbook, but doesn't explain format (e.g., 'BTC/USD'), constraints, or examples, leaving the agent with incomplete information.

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 orderbook snapshot') and resource ('for a given symbol'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_ticker' or 'get_market_summary' that also provide market data, leaving some ambiguity about when this specific tool is preferred.

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_market_summary' for market data, nor does it mention prerequisites or exclusions. It only states what the tool does, not when it should be selected.

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