Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

get_bargain

Read-onlyIdempotent

Find scoring-ranked products priced at or below a target amount, with an optional minimum to exclude cheap items and help reach free-shipping thresholds.

Instructions

送料無料ライン等の買い合わせ向けに、target_amount 円以下の商品をスコア順に返す。

「あと800円で送料無料」のような場合は min_amount=800 を指定すると、不足額に
届かない安すぎる商品を除外して、ラインを確実に超える候補だけを返せる。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bargain"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo
min_amountNo
target_amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the description only needs to add context beyond that. It adds two useful behavioral details: the results come back sorted by score, and min_amount acts as a floor that excludes candidates too cheap to close the gap. It says nothing about how the score is computed, how the limit applies, or whether pagination exists.

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 two short sentences, and the purpose comes first. The free-shipping example works well as an illustration. Nothing is bloated, but the second sentence could be tighter.

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?

There is no output schema, so the description must convey everything an agent needs. It explains the core selection logic but leaves the meaning of 'score order', the role of limit, and the role of category unexplained, which leaves the tool's behavior only partially specified.

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%. The description does explain target_amount as a price ceiling and min_amount as the floor that excludes products which are too cheap to close the gap. The other two parameters, limit and category, are not explained anywhere, so half the parameters remain undocumented.

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 states a specific verb and resource: it returns products priced at or below target_amount, in score order, for bundle purchases that need to hit a free-shipping threshold. That is clearly different from a general product search, but no sibling tool is named, so the distinction from get_deals and get_recommendations has to 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?

The description says when to use the tool and gives a concrete recipe: when the cart is about 800 yen short of free shipping, set min_amount=800. It does not say when not to use the tool or compare it with alternatives.

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