Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

danawa_prices

Compare product prices on Danawa by keyword; retrieve lowest KRW prices, brands, spec summaries, and images for purchase research.

Instructions

Return product prices from Danawa, Korea's largest price-comparison site, for a keyword: product name, lowest KRW price, brand, spec summary and image.

Args: query: Search keyword, Korean or English, e.g. "노트북" or "iPhone 16". maxItems: Maximum number of products to return (billed per product).

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": {
      "query": "<query>"
    },
    "name": "danawa_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
maxItemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/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 it does disclose two useful facts: results are billed per product, and the query works in Korean or English. It omits price freshness (live vs cached), rate limits, and failure behavior, which matter for a pricing tool.

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?

Front-loaded with the purpose and return fields, followed by a compact Args block. The phrase 'Korea's largest price-comparison site' is mild marketing filler, but the rest is tight and earns its space.

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 two-parameter keyword search with an output schema, the definition covers purpose, inputs, and cost behavior adequately. Minor gaps are the absence of result ordering and price-freshness notes, which the output schema cannot convey.

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?

Schema coverage is 0%, so the description must supply all parameter meaning. It explains that query accepts Korean or English keywords with concrete examples, and that maxItems caps returned products and drives billing — meaningful additions beyond the bare schema. It does not restate the default of 20.

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 ('Return product prices from Danawa') and enumerates the returned fields (product name, lowest KRW price, brand, spec summary, image). It is clearly distinguishable from abstract siblings like kream_prices or kurly_products by naming the source site, though it never explicitly contrasts itself with other price/ranking tools.

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 implied by the query examples ('노트북', 'iPhone 16') and the per-product billing note, which hints at cost-aware maxItems selection. There is no explicit statement of when to prefer this over other Korean commerce tools, nor any exclusion or prerequisite.

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