Skip to main content
Glama
parkyucheol-del

AlphaPipeline

by parkyucheol-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

market.kimchi_alert

Identify Korea-vs-global crypto arbitrage: check if a coin trades at a premium or discount on Upbit, plus reverse-premium crash risk and premium surge alerts.

Instructions

Detect Korea-vs-global crypto price arbitrage (the "kimchi premium"):
whether a coin trades at a premium or discount on Upbit vs a global
reference price (Coinbase spot, CoinGecko fallback - NOT a live Binance
orderbook, despite the legacy binance_price_usdt field name kept for
backward compatibility), a reverse-premium crash-risk flag (-1.5% or
below), and a premium-surge flag (+3 percentage points within the last
hour).

Use this when asked about cross-exchange arbitrage opportunities in Korean
crypto markets, to detect a reverse-premium crash risk, or a sudden premium
surge. This is a live snapshot only - do NOT use it for historical/backtesting
data, or for non-Korean-exchange comparisons (use arb.spread_matrix for a
general CEX-DEX spread check instead).

Args:
    symbol: Ticker symbol, e.g. "BTC", "ETH", "SOL" (default "BTC").

Returns:
    On success: {"success": true, "symbol", "upbit_price_krw",
        "binance_price_usdt" (legacy name, actually Coinbase/CoinGecko),
        "cex_reference_price_usdt" (same value, honest name),
        "cex_price_source", "kimchi_premium_pct", "premium_change_1h_pct",
        "alerts", "thresholds", "notice", ...}
    On failure: {"success": false, "error": {"type", "message"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and handles it thoroughly. It reveals that the tool is a 'live snapshot only', that binance_price_usdt is a legacy name actually backed by Coinbase/CoinGecko and 'NOT a live Binance orderbook', and discloses the exact thresholds for the crash-risk and surge flags. It also documents the success/failure return shapes, including the error structure.

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 organized into clear sections: what it does, when to use/not use, args, and returns. Every sentence carries necessary information, including the critical caveat about the legacy field name and the fallback reference source. There is no fluff or repeated schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully documents the return payload by listing success fields (including the honest cex_reference_price_usdt alias), the failure error structure, and the alert thresholds. Combined with the single well-explained parameter, nothing an agent needs to invoke it correctly or interpret results is missing.

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

Parameters5/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, and it does: 'symbol: Ticker symbol, e.g. BTC, ETH, SOL (default BTC)'. This adds semantic meaning beyond the raw schema field and gives concrete examples. The single parameter is fully explained for an agent.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Detect Korea-vs-global crypto price arbitrage (the kimchi premium)' and explains the Upbit-vs-global-reference comparison, including the two flags. It explicitly names arb.spread_matrix as the tool for non-Korean comparisons, distinguishing itself from the sibling set. This is purpose clarity at the highest level.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states 'Use this when asked about cross-exchange arbitrage opportunities in Korean crypto markets' and gives explicit when-not-to-use cases: 'do NOT use it for historical/backtesting data, or for non-Korean-exchange comparisons'. It names the alternative tool (arb.spread_matrix) for the general CEX-DEX spread check. This is fully explicit when/when-not/alternatives guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools