Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

glowpick_rankings

Retrieve K-beauty product rankings and reviews from a Korean cosmetics community as clean English JSON, with configurable time-window and product-count limits.

Instructions

Return Glowpick (Korean cosmetics ranking & review community) K-beauty rankings and reviews as clean English JSON.

Args: monthTerm: Ranking time window in months, e.g. "24". maxProducts: Maximum number of products 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": "glowpick_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthTermNo24
maxProductsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a meaningful trait beyond the schema: results are normalized to clean English JSON from a Korean-language source, which matters for downstream use. It says nothing about pagination, coverage limits, freshness, or failure modes, leaving real behavioral gaps.

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?

Two short sections — a one-line purpose statement followed by an Args list — with no filler. The purpose is front-loaded, though the arguments are formatted as a docstring block rather than prose an agent can parse as guidance.

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?

With an output schema present, return values need not be explained, and both optional parameters are covered. What is missing is routing context against the large set of sibling ranking/review tools and any hint about result volume or language handling guarantees.

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 is the only documentation for both parameters, and it does explain monthTerm (ranking time window in months, example "24") and maxProducts (maximum products returned). This is adequate but thin: it does not clarify the string-typed monthTerm's accepted range/format, defaults, or what maxProducts caps relative to available data.

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: returns Glowpick K-beauty rankings and reviews as English JSON, and identifies the source community (Korean cosmetics ranking & review). That plus the domain naming lets an agent distinguish it from siblings like musinsa_rankings or oliveyoung_rankings without opening a schema, though it never explicitly contrasts itself with them.

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 or when-not-to-use guidance and no mention of alternatives among the many ranking/review siblings. The agent must infer that this tool is the Glowpick-specific option purely from the parenthetical identifying the community.

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