Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

musinsa_rankings

Retrieve Musinsa fashion rankings or product search results as clean English JSON, filtered by category or keyword, gender, and item limit.

Instructions

Return Musinsa (Korea's largest online fashion platform) rankings and products as clean English JSON.

Args: mode: One of "ranking" or "search". query: Category code (e.g. "001") or search keyword depending on mode. gender: Gender filter, e.g. "A" (all), "M", "F". 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": "musinsa_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoranking
queryNo001
genderNoA
maxItemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions returning "clean English JSON" (a normalization/translation hint) but says nothing about auth, rate limits, scraping freshness, or what happens on invalid category codes or oversized maxItems. For an unannotated tool this is a significant gap.

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 and scannable with one line per parameter. Slight redundancy with the schema titles, but nothing that wastes meaningful space.

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?

The output schema exists, so return values need not be explained, and parameters are reasonably covered. What remains missing for a 4-parameter, unannotated data-fetching tool is error behavior, item-limit caps, and any guidance on mode selection, leaving it adequate but not complete.

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?

With 0% schema description coverage, the description does real work: it explains that mode is "ranking" or "search" (an enum the schema lacks), that query is a category code like "001" or a keyword depending on mode, and gives gender values ("A", "M", "F"). It stops short of documenting maxItems limits or defaults, but it substantially compensates for the empty schema.

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 Musinsa rankings and products") and names the platform explicitly, which distinguishes it from the other Korean-commerce siblings by source. However, it does not articulate what separates ranking mode from search mode at the purpose level, leaving the dual nature of the tool somewhat implicit.

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; the agent must infer that this tool is for Musinsa specifically versus the many sibling rankings tools. The only hint of usage is the mode argument description, which is parameter-level rather than tool-level guidance.

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