Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

kream_prices

Retrieve KREAM sneaker, streetwear, and luxury resale rankings and prices as clean English JSON, filtered by period (realtime, daily, weekly) and item count.

Instructions

Return KREAM (Korea's leading sneaker/streetwear/luxury resale platform) ranking and resale prices as clean English JSON.

Args: period: Ranking period, e.g. "realtime", "daily", "weekly". maxItems: Maximum number of items to return.

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": "kream_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNorealtime
maxItemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it: nothing is said about authentication, rate limits, geographic scope, whether 'realtime' data is cached, or how rankings are ordered. The only behavioral claim is "clean English JSON," which is thin. It does not contradict anything, but it leaves major operational questions unanswered.

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 purpose statement is front-loaded and the Args block is compact and scannable. The parenthetical platform gloss is worth its words for disambiguation. No filler sentences, though the quoting style and mixed prose/Args formatting is slightly rough.

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?

An output schema exists, so return values need not be described, and the two parameters are covered. What remains missing for an unannotated tool is the operational envelope: pagination, data freshness, and how period interacts with ranking type. Adequate but with clear gaps against a tool of this complexity.

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 description coverage is 0%, so the description must compensate. It does partially: it gives example values for period ("realtime", "daily", "weekly"), which meaningfully extends a bare string parameter with a default. For maxItems it only restates the schema ("Maximum number of items to return") without bounds, ceilings, or behavior when omitted.

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 gives a specific verb ("Return") plus a well-defined resource (KREAM rankings and resale prices) and even characterizes the platform as Korea's sneaker/streetwear/luxury resale marketplace. That domain framing lets an agent distinguish it from a general shopping or fashion-ranking sibling. It stops short of naming an alternative, so it does not reach a 5.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the text. The agent must infer that this is the KREAM-specific source versus siblings such as musinsa_rankings or danawa_prices purely from the platform name. No prerequisites or context conditions are stated.

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