supershopping

슈퍼쇼핑 상품 검색

search_products

Read-onlyIdempotent

자연어로 신품·중고 통합 상품 검색 (슈퍼쇼핑의 기본 진입점).

언제: 사용자가 특정 상품을 찾을 때. 예) "남성 패딩 20만원 이하", "중고 RTX 4070", "27인치 게이밍 모니터". 자동 처리: 도메인(패션/전자)·성별·가격대·속성을 질의에서 추출해 필터링. 반환: {items: [{title, min_price, key_specs, thumbnail, buy_url, source, condition, ...}], total}. → 결과 제시 시 각 buy_url을 링크로 함께 보여줘라. 사진은 get_product_image로 렌더. 추천만 원하거나 검색어가 모호하면 recommend_products를 써라.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`category`	No
`max_price`	No
`min_price`	No
`attributes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false. The description adds behavioral context: automatic extraction of domain, gender, price, attributes; return structure; and instruction to use get_product_image for images. 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?

The description is relatively concise, front-loads purpose and usage, and includes examples. It covers multiple aspects without excessive verbosity.

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 6 parameters, 0% schema coverage, and output schema present, the description provides purpose, usage, and return format. However, it lacks detailed explanation of explicit parameters like category and attributes beyond automatic extraction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description should compensate. It mentions query is natural language and limit has default 10, but does not explain category, max_price, min_price, or attributes. Automatic extraction is mentioned, but explicit parameter roles are unclear.

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 specifies it is a natural language search tool for new and used products, and it is the basic entry point for Super Shopping. Examples illustrate usage, and it distinguishes from recommend_products.

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?

The description explicitly states when to use (user looking for specific product) and when not to (ambiguous query or recommendations wanted, pointing to recommend_products). It also notes automatic extraction of filters.

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?