Skip to main content
Glama

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

by io.github.juh5ng
OverviewDiscussionsAdmin

kimchi_premium_history

Time series of the kimchi premium from the recorded archive, both bases, newest-last. Params: ?symbol=BTC &window=1h|6h|24h|7d|30d|90d &points=500 (max 2000) &before=<next_before>. Each page is a separate paid request. Continue while has_more is true using next_before. Inspect actual archive depth and freshness through /api/preview/premium-coverage before buying. Costs $0.08 in USDC per call, settled via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beforeNoUnix-second cursor from next_before; returns older rows strictly before it
pointsNoMax points returned (default 500, max 2000)
symbolNoArchived tickers: BTC, ETH, XRP, SOL, DOGE, USDT
windowNoLookback window (default 24h)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / before
      Added value: +{
+  "description": "Unix-second cursor from next_before; returns older rows strictly before it",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • removedInput schema / properties / before
      Removed value: -{
-  "description": "Unix-second cursor from next_before; returns older rows strictly before it",
-  "type": "integer"
-}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: each page is a separate paid request, cost is $0.08 USDC settled via x402, pagination proceeds via next_before, and rows are newest-last. The main omission is return shape beyond has_more/next_before.

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?

A single front-loaded paragraph that leads with what the tool returns, then pagination, then cost. Some space is spent re-listing parameters already in the schema, which is mild redundancy but not bloat.

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 paid, paginated archive tool with no annotations and no output schema, the description covers the essentials an agent needs: payment cost and mechanism, pagination continuation rule, ordering, and a pre-purchase coverage check. Only the concrete response fields are left implicit.

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?

Schema coverage is 100%, so each of the four parameters is already documented with defaults, enums, and cursor semantics. The description restates the same parameter syntax without adding format or behavioral meaning beyond linking before to next_before, which the schema already notes.

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 and resource: a time series of the kimchi premium drawn from the recorded archive, newest-last. The word 'history' plus 'recorded archive' clearly separates it from the live kimchi_premium and kimchi_premium_stats siblings, though it never names them explicitly.

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?

Gives concrete operating guidance: continue while has_more is true using next_before, and check archive depth/freshness via the premium-coverage preview endpoint before buying. It stops short of stating when to prefer this over the snapshot siblings, so it is strong context rather than full when/when-not routing.

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