Skip to main content
Glama
accentist

BuyKing MCP Server

by accentist
OverviewSchemaSourceRelated ServersDiscussions(3)Admin
JavaScript
Hybrid

search_buyking_semantic_KR

Search hot deals available for direct shipping to South Korea, with KRW pricing and Korean-language results from Coupang, 11st, Gmarket, and more.

Instructions

[한국 전용] 한국 내 직배송 가능한 핫딜만 검색합니다. KRW(₩) 가격, 한국어 결과. 사용자가 한국에 있거나 한국 배송 상품을 원할 때 사용하세요. 쿠팡, 11번가, G마켓, 옥션, 알리익스프레스 등 국내외 쇼핑몰의 핫딜을 검색합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo정렬 조건. 기본값은 관련도순이며, 가격순 정렬 요청 시 'price_asc' 등을 사용. (허용값: 'newest', 'price_asc', 'price_desc', 'click_desc')
keywordYes사용자의 질문에서 핵심이 되는 상품명 키워드. (예: '무소음 마우스', '제로 콜라', '여름 이불'). 자연어 문장이 아닌 명사 위주로 핵심만 추출할 것.
categoryNo상품의 카테고리 필터. 확실한 경우에만 사용하고 모르면 생략할 것. (허용값: 'all', '💻 IT/가전/디지털', '👚 패션/뷰티/잡화', '🍎 식품/생활/리빙', '📚 도서/여행/취미', '🛒 종합몰/기획전', '📦 기타')
platformNo특정 쇼핑몰을 지정했을 때만 사용. (허용값: 'all_rank', 'coupang', '11st', 'gmarket', 'auction', 'aliexpress')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the scope (Korea-only, direct shipping, KRW, Korean results) but does not disclose behaviors like default sort order, result limits, or return format. For a read-oriented search tool, this is adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the most important scoping information (Korea-only, direct shipping, KRW). No filler or redundancy. Every sentence earns its place.

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?

Given the 4 parameters are fully documented in the schema and no output schema exists, the description provides sufficient context for usage and scope. The only gap is the return format, which is not critical for a search tool. Overall, it is complete enough for an agent to call correctly.

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 100%, so the baseline is 3. The description adds no parameter-specific details beyond the schema; it only provides contextual scope (KRW, Korean results) that doesn't map to a particular parameter. No additional semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('search') with a clear scope: Korea-only direct-shipping hot deals, KRW prices, and Korean results. It explicitly distinguishes itself from the US and JP siblings by name and region, so an agent can immediately tell it apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states when to use: 'when the user is in Korea or wants Korea shipping.' It does not explicitly list exclusions or mention the US/JP alternatives, but the regional scope makes the choice obvious given sibling names. Could be more explicit about the alternatives, but it's sufficient.

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

Deploy Server

Other Tools