Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

kurly_products

Search Market Kurly grocery products by keyword and return clean English JSON with sorting, result limits, and optional brand enrichment.

Instructions

Return Market Kurly (Korea's premium grocery/e-commerce platform) grocery and product data as clean English JSON.

Args: mode: Mode, e.g. "search". query: Search keyword. Empty applies actor default. maxItems: Maximum number of products to return. sort: Sort order, e.g. "RECOMMENDED". enrichBrand: Whether to enrich results with brand-level detail.

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

Input Schema

NameRequiredDescriptionDefault
modeNosearch
sortNoRECOMMENDED
queryNo
maxItemsNo
enrichBrandNo

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 disclosure burden. It notes the empty-query default and that output is 'clean English JSON', but says nothing about valid modes beyond 'e.g. search', rate limits, result caps, or whether enrichBrand triggers extra calls or cost. For a multi-mode scraping tool with zero annotation coverage, this leaves major behavioral 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 sentence is front-loaded and the Args block is compact with one line per parameter. Nothing is redundant, though the 'e.g.' hedges waste space where concrete enumerations would be more useful.

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

Completeness2/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 explained, but the mode parameter governs the tool's entire behavior and its allowed values are neither in the schema (no enums) nor the description. For a five-parameter, mode-driven tool with no annotations, an agent is left guessing at the most consequential input.

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, and it does document all five parameters at a surface level. However, the two behaviorally critical ones are underspecified: mode is only 'e.g. "search"' and sort only 'e.g. "RECOMMENDED"', so the agent still cannot know the valid value sets. This is partial compensation for a full coverage gap.

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 names a specific verb and resource ('Return Market Kurly ... grocery and product data as clean English JSON') and identifies the platform, which implicitly separates it from sibling tools covering other Korean sources. It stops short of explicitly contrasting with alternatives, but the platform identity is a strong differentiator.

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 statement of when to use this tool versus the sibling shopping/ranking tools, nor any prerequisite or exclusion. The only usage hint is that an empty query 'applies actor default', which is a default-behavior note rather than guidance on selecting this tool.

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