Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

get_deals

Read-onlyIdempotent

Retrieve current Amazon sale products, filtered and sorted by discount, score, price, brand, query, category, or sale type, with pagination for browsing more results.

Instructions

現在セール中の商品を返す。

sort は recommended(既定。スコアを主・割引率を従としたバランス順)/
savings(割引率順)/ score(スコア順)/ price_asc(安い順)。
割引率の高い商品には低スコアのものが混ざりやすいため、既定でスコア70点以上に
絞っている。全件を確認したい場合は min_score=0 を指定すること。
brand / query / max_price でも絞れる。offset で続きのページを取得できる。

セールの種類は各商品の deal_badge(例: タイムセール / プライム会員限定セール /
ブラックフライデー)で区別される。sale_type に種別名の一部(例: ブラック
フライデー、プライム)を渡すと、そのバッジの商品だけに絞れる。応答の
available_badges には、sale_type 以外の現在の条件に合う範囲で開催中の
セール種別と件数が入る(結果が0件のときに、存在しないセール種別が
件数つきで返ることはない)。

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_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorecommended
brandNo
limitNo
queryNo
offsetNo
categoryNo
max_priceNo
min_scoreNo
sale_typeNo
min_savings_percentageNo

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds behavior that is not in the annotations: the hidden default filter of score >= 70, the rationale for that filter, and the fact that the response carries an available_badges list scoped to the current non-sale_type filters. It never explains limit behavior or result ordering stability across pages, which is why it is 4 rather than 5.

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 front-loaded with the purpose, then groups sort modes, then filters, then the sale_type/available_badges explanation. Each paragraph earns its place, and the parenthetical about available_badges prevents a real misinterpretation. The wording is slightly dense — nested parentheticals in the sort sentence — 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?

With 10 parameters, no required fields, no output schema, and no per-parameter schema text, the description still manages to explain the non-obvious semantics: the default score floor, the sort modes, and the shape of available_badges in the response. The gaps on limit, category, and min_savings_percentage are real but low-risk, since their names and defaults are self-explanatory.

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% across 10 parameters, so the description has to carry the meaning. It explains sort's four modes, including what 'recommended' balances, and it covers min_score, sale_type, brand, query, max_price, and offset. It says nothing about limit, category, or min_savings_percentage, leaving three parameters defined only by their names and defaults.

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 opening line states a specific verb and resource: it returns products that are currently on sale. That is far more precise than a sibling name like search_products or get_recommendations would imply. The description never explicitly contrasts itself with get_bargain or search_products, which keeps it from a 5.

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 gives concrete in-tool guidance: sort defaults to 'recommended'; the default min_score=70 exists because high-discount items often score low; and passing min_score=0 returns everything. It also explains pagination via offset and how to narrow by sale_type. It stops short of saying when to choose this tool over a sibling such as get_bargain, so it earns a 4 rather than a 5.

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