Skip to main content
Glama
solangii

Upbit MCP Server

get_market_summary

Retrieve summary information for major cryptocurrency markets to analyze current trading conditions and make informed decisions.

Instructions

주요 암호화폐 시장의 요약 정보를 제공합니다.

Returns:
    dict: 주요 암호화폐 시장 요약 정보

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_market_summary' tool. It fetches all KRW markets, retrieves ticker data in chunks, filters major coins, computes top volume (excluding majors), top gainers, and top losers, and returns a summary dictionary.
    async def get_market_summary(ctx: Context = None) -> dict:
        """
        주요 암호화폐 시장의 요약 정보를 제공합니다.
        
        Returns:
            dict: 주요 암호화폐 시장 요약 정보
        """
        async with httpx.AsyncClient() as client:
            # 마켓 정보 가져오기
            markets_res = await client.get(f"{API_BASE}/market/all")
            if markets_res.status_code != 200:
                if ctx:
                    ctx.error(f"마켓 정보 조회 실패: {markets_res.status_code}")
                return create_error_response("마켓 정보 조회에 실패했습니다.", markets_res.status_code)
            
            all_markets = markets_res.json()
            krw_markets = [market for market in all_markets if market["market"].startswith("KRW-")]
            
            # 티커 정보 가져오기 (50개씩 나누어 요청)
            all_tickers = []
            chunk_size = 50
            
            for i in range(0, len(krw_markets), chunk_size):
                chunk = krw_markets[i:i+chunk_size]
                markets_param = ",".join([market["market"] for market in chunk])
                
                ticker_res = await client.get(f"{API_BASE}/ticker", params={"markets": markets_param})
                if ticker_res.status_code != 200:
                    if ctx:
                        ctx.warning(f"일부 티커 정보 조회 실패: {ticker_res.status_code}")
                    continue
                    
                all_tickers.extend(ticker_res.json())
            
            # 주요 코인 정보
            major_coin_info = [ticker for ticker in all_tickers if ticker["market"] in MAJOR_COINS]
            
            # 상위 거래량 코인 (주요 코인 제외)
            volume_sorted = sorted([t for t in all_tickers if t["market"] not in MAJOR_COINS], 
                                  key=lambda x: x["acc_trade_price_24h"], 
                                  reverse=True)
            top_volume_coins = volume_sorted[:5]
            
            # 상위 상승률 코인
            price_change_sorted = sorted(all_tickers, key=lambda x: x["signed_change_rate"], reverse=True)
            top_gainers = price_change_sorted[:5]
            
            # 상위 하락률 코인
            top_losers = price_change_sorted[-5:]
            
            return {
                "timestamp": all_tickers[0]["timestamp"] if all_tickers else None,
                "major_coins": major_coin_info,
                "top_volume": top_volume_coins,
                "top_gainers": top_gainers,
                "top_losers": top_losers,
                "krw_market_count": len(krw_markets)
            }
  • main.py:50-50 (registration)
    The registration of the get_market_summary tool using the FastMCP mcp.tool() decorator.
    mcp.tool()(get_market_summary)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool returns ('주요 암호화폐 시장 요약 정보') without describing what that summary contains, how current the data is, whether it's cached or real-time, rate limits, authentication requirements, or error conditions. For a market data tool with zero annotation coverage, this is insufficient behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with two sentences that directly state the purpose and return type. The first sentence clearly states what the tool does, and the second specifies the return format. There's no unnecessary information or repetition. However, the Korean-to-English translation in the Returns section creates minor redundancy.

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 and the absence of both annotations and output schema, the description is incomplete. It doesn't explain what 'summary information' includes (e.g., market caps, volumes, top gainers/losers, overall trends), the scope of 'major cryptocurrencies,' data freshness, or format details. For a tool that presumably returns structured market data, more context is needed about what the agent can expect.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of parameters. The description appropriately doesn't discuss parameters since none exist. The baseline for 0 parameters with full schema coverage is 4, as there's nothing to compensate for and the description doesn't incorrectly mention parameters.

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 tool's purpose: '주요 암호화폐 시장의 요약 정보를 제공합니다' (Provides summary information of major cryptocurrency markets). It specifies the verb '제공합니다' (provides) and the resource '주요 암호화폐 시장 요약 정보' (major cryptocurrency market summary information). However, it doesn't explicitly differentiate from sibling tools like get_ticker or get_orderbook, which also provide market-related information.

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 makes this 'summary' different from other market data tools like get_ticker (single asset price), get_orderbook (depth data), or get_trades (recent transactions). There's no context about when this aggregated view is preferable to more detailed tools.

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