Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

find_similar_products

Read-onlyIdempotent

Returns same-category alternatives for a specified product when it is out of stock or over budget, so you can present replacement options without searching again.

Instructions

指定商品と同カテゴリの代替候補を返す。

目的の商品が在庫切れ・予算超過のときに、探し直さずに代替案を提示するために使う。
max_price 未指定の場合は、対象商品の価格の0.5〜1.5倍の価格帯にある候補を
優先し、各価格帯の中ではスコア順に並べる。min_score で候補の最低スコアも
指定できる。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asin": "<asin>"
    },
    "name": "find_similar_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes
limitNo
max_priceNo
min_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description earns credit for disclosing actual result-shaping logic — the 0.5–1.5x price band applied when max_price is omitted, and score-ordered ranking within each price band — which an agent cannot get from annotations.

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 comes first, followed by the usage trigger and then the ranking rules — a sensible front-loaded order with no filler. The line breaks mid-sentence are a minor readability cost rather than wasted content.

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?

With four simple parameters, no output schema, and annotations covering safety, the description supplies what is missing: the default price-band heuristic and the scoring concept. It omits what a returned candidate actually contains (ASIN, price, score) and any cap/limit behavior, which is a modest remaining gap.

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 must carry parameter meaning, and it does explain max_price's implicit default range and what min_score filters on. However, 'asin' (the required identifier) and 'limit' (default 5) are never addressed, leaving half the parameters undocumented anywhere.

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?

The description opens with a specific verb and resource ('指定商品と同カテゴリの代替候補を返す'), which tells an agent exactly what comes back and constrains it to same-category substitutions. It does not explicitly contrast itself with siblings like search_products or get_recommendations, so differentiation must be inferred.

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 names the triggering conditions clearly: when the target item is out of stock or over budget, use this instead of re-searching. That is actionable context, but it stops short of naming an alternative tool or stating when it should not be used.

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