Skip to main content
Glama
solangii

Upbit MCP Server

get_ticker

Retrieve current market price and trading data for a cryptocurrency from Upbit to inform trading decisions and monitor market movements.

Instructions

Get the latest ticker data from Upbit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • The main handler function for the 'get_ticker' tool. It makes an async HTTP GET request to the Upbit API ticker endpoint with the given symbol and returns the JSON response.
    async def get_ticker(symbol: str) -> dict:
        """Get the latest ticker data from Upbit"""
        url = f"{API_BASE}/ticker"
        async with httpx.AsyncClient() as client:
            res = await client.get(url, params={"markets": symbol})
            return res.json()[0]
  • main.py:42-42 (registration)
    Registration of the get_ticker tool function with the FastMCP server using the mcp.tool() decorator.
    mcp.tool()(get_ticker)
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 states it 'gets' data, implying a read-only operation, but doesn't cover critical aspects like rate limits, authentication needs, response format, or potential errors. This is a significant gap for a tool with zero annotation coverage.

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 purpose 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 financial data retrieval, no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on behavior, output, and parameter meaning, making it inadequate for effective tool use in this context.

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?

The schema description coverage is 0%, and the description adds no information about the 'symbol' parameter beyond what the schema provides (a required string). It doesn't explain what 'symbol' represents (e.g., a trading pair like 'BTC-KRW'), format expectations, or examples, failing to compensate for the low coverage.

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 verb ('Get') and resource ('latest ticker data from Upbit'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'get_market_summary' or 'get_orderbook', which likely provide different financial data, so it misses full sibling differentiation.

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. It doesn't mention what 'ticker data' includes compared to other data retrieval tools in the sibling list, such as 'get_market_summary' or 'get_orderbook', leaving the agent 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/solangii/upbit-mcp-server'

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