Skip to main content
Glama
Sign In

K-Data — Korean Sell-Side Research & Market Data

by io.github.juh5ng
OverviewDiscussionsAdmin

crypto_krw_ticker

Live quote for one Upbit KRW market by ticker symbol (e.g. BTC, ETH, XRP): price, 24h change, 24h high/low, 24h traded value in KRW. Costs $0.005 in USDC per call, settled via x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "crypto_krw_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesCoin ticker symbol, e.g. BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden. It discloses a key behavioral trait: each call costs $0.005 in USDC settled via x402. It also states what data will be returned. It does not cover invalid-ticker behavior, but for a read-only quote tool the important transparency is present.

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 two tight sentences: the first front-loads the tool's purpose, scope, and output fields; the second provides the critical cost and settlement detail. Every clause earns its place.

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

Completeness4/5

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

For a single-parameter tool with no output schema, the description covers the returned fields, market scope, and pricing—enough for an agent to invoke it correctly. Minor gaps are the lack of guidance for discovering valid tickers and behavior on invalid symbols, but these do not block correct use.

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

Parameters3/5

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

The single parameter is already fully documented in the schema ('Coin ticker symbol, e.g. BTC') with 100% coverage. The description adds examples and market context, but no new semantic constraints, formatting rules, or enumeration, so the baseline of 3 applies.

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 uses a specific verb ('Live quote') and a precise resource ('one Upbit KRW market by ticker symbol'), with concrete examples and the exact data fields returned. This clearly distinguishes it from siblings like crypto_krw_markets, which lists markets, and fx_usdkrw, which covers USD/KRW FX rates.

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

Usage Guidelines4/5

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

The description clearly establishes the context: use this tool for a single Upbit KRW market quote identified by ticker. However, it does not explicitly state when not to use it or point to crypto_krw_markets as the way to discover valid tickers, so it stops short of a 5.

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

All K-Data — Korean Sell-Side Research & Market Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources