Skip to main content
Glama

Polymarket, Kalshi, Hyperliquid Funding Arbitrage & DEX Swap MCP

Check South Korea KRW Kimchi Premium & USDT FX

check_krw_kimchi_premium
Read-onlyIdempotent

Checks live South Korean Upbit KRW spot prices and KRW-USDT Tether implied FX against global USD perpetual mark prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_krw_kimchi_premium"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that the data is 'live' and names the venues (Upbit KRW spot vs global perp mark), which is useful context, but it does not say whether the premium is computed for you, how fresh the quotes are, or what the response contains. With annotations doing the heavy lifting, a 3 is appropriate.

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?

A single front-loaded sentence with no filler, preamble, or redundant restatement of the title. Every clause names a distinct data source used in the computation.

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

Completeness3/5

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

With no output schema and no parameters, the description is the only place to explain what comes back. It names the inputs to the calculation but never says the result is a premium percentage plus an implied FX rate, nor does it note refresh/latency characteristics, which matters for a 'live' market-data tool.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool is 4, and the description correctly implies it runs on defaults with no input needed.

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?

States a specific verb ('Checks') and specific resources: Upbit KRW spot prices, KRW-USDT implied FX, and global USD perpetual mark prices. That is far more informative than the name alone and an agent can tell what data it returns. It stops short of positioning itself against siblings such as scan_perp_funding_spreads or compare_pendle_fixed_vs_funding.

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

Usage Guidelines3/5

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

Usage is only implied by the resource named (you would call this to observe the Korean kimchi premium / implied USDT FX). There is no explicit when-to-use statement, no when-not-to-use, and no mention of the sibling tools it might be confused with.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.