Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

get_recommendations

Read-onlyIdempotent

Returns recommended products that score 90 or higher on an independent rating scale. Use it to find top-rated items, optionally filtered by category and limited in count.

Instructions

独自スコア90点以上の高評価おすすめ商品を返す。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description contributes one genuinely new behavioral fact — the 90-point score threshold that defines the result set — but says nothing about ordering, result count behavior, or how the proprietary score is derived. That is a modest but real addition on top of the 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?

A single short sentence with no filler, and the quality criterion is front-loaded before the return verb. It is efficient, though its brevity borders on under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter listing tool with no output schema and no sibling differentiation, the description leaves too much unsaid: parameter meaning, result ordering, and how it differs from the other discovery tools. Only the score threshold gives the agent something actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the burden for limit and category, and it does not mention either. An agent cannot tell from this text what category values are accepted or how limit interacts with the fixed quality threshold. The threshold mentioned is a data filter, not a parameter, so it does not compensate.

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 names a specific verb (返す) and resource (おすすめ商品) and adds a concrete selection criterion (独自スコア90点以上), so the agent knows exactly what population is returned. It stops short of differentiating this from siblings like get_deals or get_bargain, which also surface curated product sets.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus the deal/bargain/search siblings, and no prerequisites or exclusions. The only implied guidance is that this returns high-rated recommendations, leaving the agent to guess whether to prefer get_deals for discounts or search_products for targeted queries.

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