supershopping

슈퍼쇼핑 상품 추천

recommend_products

Read-onlyIdempotent

슈퍼쇼핑에서 의도·예산 기반 상품 추천 + 추천 근거.

언제: 사용자가 구체적 검색어 없이 용도/취향/예산만 말할 때("겨울 데이트룩 추천", "50만원대 가성비 노트북"). 인자: intent(용도/취향), budget(예산 상한), must_have(필수 조건). 반환: {recommendations: [{title, min_price, reason, buy_url, thumbnail, source}], affiliate_disclosure?}. → 각 추천을 buy_url 링크와 함께 제시하고, 사진은 get_product_image로 보여줘라.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`budget`	No
`intent`	Yes
`must_have`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, confirming safe read operation. The description adds behavioral details: returns recommendations with rationale, field structure, and suggests using get_product_image for photos. No contradictions.

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?

Description is well-structured with bullet points and clear sections. It is concise but includes all necessary information. Slightly verbose due to Korean and English mix, but overall effective.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations provide safety profile, the description is complete. It covers usage, parameter meanings, and return format. Even includes guidance on using get_product_image for images.

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 description must compensate. It explains intent, budget, and must_have with meanings in Korean, but omits the limit parameter (default 5). Also does not clarify nullability for budget and must_have. Partial coverage leaves a gap.

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 clearly states it recommends products based on intent and budget, and distinguishes from sibling tools like search_products (specific query) and recommend_outfit (likely fashion-focused). The verb 'recommend' and resource 'products' are explicit.

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

Usage Guidelines5/5

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

Explicitly states when to use: when user provides only purpose/taste/budget without specific search terms. Implies not for exact product queries, suggesting alternatives like search_products.

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

All supershopping tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: market analysis, product comparison, detail retrieval, image fetching, checkout initiation, outfit recommendation, general recommendation, and search. Descriptions and usage contexts disambiguate effectively.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., analyze_market, compare_products) using lowercase with underscores, making them predictable and easy to differentiate.

Tool Count5/5

With 8 tools covering search, recommendation, comparison, details, images, market analysis, and checkout, the count is well-scoped for a comprehensive shopping assistant without being overwhelming.

Completeness4/5

The tool surface covers the main shopping workflow—search, recommend, compare, view details, images, market analysis, and checkout. Minor gaps like category listing or user-specific features are absent but not critical for the core purpose.

Resources

Need Help?