Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

compare_products

Read-onlyIdempotent

Compare two to five products side by side to view pros, cons, prices, and scores, plus a summary of the cheapest option and score differences for faster buying decisions.

Instructions

2〜5件の商品を比較しやすい形で並べて返す。

各商品には採点根拠から抽出した pros(加点理由)/ cons(減点理由)が付き、
応答には comparison_summary(最安・最高スコア・価格差・スコア差)が含まれる。

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": {
      "asins": "<asins>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds genuine behavioral value the annotations do not: each result carries pros/cons derived from scoring rationale, and the response includes comparison_summary with cheapest, top score, price spread and score spread. It does not mention error behavior for invalid or out-of-range ASINs, which is the remaining gap.

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?

Three short lines, front-loaded with the core action, followed by the enrichment (pros/cons) and the response summary. No filler or restatement of the name.

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 no output schema, the description takes on the burden of describing returns, and it does so concretely via pros/cons and the comparison_summary fields. Combined with annotations covering the safety profile, the definition is nearly complete; only input validation/error semantics are unstated.

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?

There is a single parameter (asins) with 0% schema description coverage and no minItems/maxItems, so the description must compensate. It does supply the useful 2-5 item count constraint, but never states that the input is a list of ASINs or what an ASIN is, leaving the parameter's meaning only half-covered.

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: arranges 2-5 products in a comparable form and returns them, with pros/cons and a comparison_summary. The scope (2-5 items, comparison output) is concrete. It stops short of explicitly contrasting with siblings such as find_similar_products or get_product, so differentiation is left implicit.

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

Usage Guidelines3/5

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

The '2〜5件' constraint implies when this tool is appropriate (multi-product comparison rather than single lookup or discovery). However, there is no explicit when-to-use/when-not guidance and no naming of alternatives like get_product for a single item, so the agent must infer the routing.

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