Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

get_product

Read-onlyIdempotent

Retrieves detailed Amazon product information by ASIN, including summary, specifications, stock status, research date, and score rationale when available.

Instructions

ASINで1商品の詳細(要約・スペック・在庫・調査日、あればスコア根拠)を返す。

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": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds value beyond them by disclosing the returned payload (summary, specs, stock, survey date, and score rationale when available) – important because there is no output schema – and by flagging that the score rationale is conditional rather than always present.

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?

One compact sentence with the scope (1商品) and the identifier (ASIN) front-loaded and no filler. It is arguably too terse for the number of concepts packed into a parenthetical, but nothing is wasted.

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?

For a single-parameter, no-output-schema lookup whose annotations cover the safety profile, the description supplies the essentials: input key, returned fields, and the conditional nature of the score rationale. The remaining gap is failure behavior (invalid/unknown ASIN) and freshness semantics of 調査日, which keeps it short of full completeness.

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 coverage is 0%, so the description must carry the parameter meaning. Saying the lookup is done 'ASINで' does establish that the single string parameter is an Amazon ASIN, which is more than the bare 'Asin' schema title, but it gives no format example, casing rules, or error behavior for a malformed ASIN.

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 (返す/return) and resource (1商品の詳細 – a single product's details) keyed by ASIN, and enumerates the content (要約・スペック・在庫・調査日・スコア根拠). That is enough for an agent to tell it apart from listing/search siblings such as search_products or get_deals, though no sibling is named explicitly.

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?

Usage is only implied: the agent must infer that this is the tool for fetching one known product when it already holds an ASIN. There is no statement of when to prefer it over compare_products or get_recommendations, and no note about what to do if the ASIN is unknown.

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