Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

list_brands

Read-onlyIdempotent

Search brands by partial name, group, or slug, automatically handling Japanese-English variations and returning listing counts for product comparison.

Instructions

ブランドを検索する(部分一致、またはブランドグループ名/スラッグ。日英表記ゆれは自動で吸収する)。各ブランドの掲載件数つき。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: automatic absorption of Japanese/English spelling variants and the fact that each result carries a listing count per brand. It does not mention pagination or what the default limit does.

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?

Two short sentences with the core action first and the match/normalization detail and return payload compactly bracketed. Dense but no filler; nothing is buried or repeated.

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?

For a simple two-optional-param read with no output schema, the description covers query semantics and hints at the returned counts, but leaves the limit/pagination behavior and full result shape unexplained, so it is adequate rather than complete.

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%, so the description must carry the load. It usefully explains that `query` accepts partial strings, brand-group names, or slugs and tolerates JP/EN variance, but says nothing about `limit` (default 50) or its pagination effect, leaving one of two parameters 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?

Names a specific verb+resource (search / brands) and adds matching semantics (partial match, brand-group name or slug, JP/EN spelling normalization). Siblings like list_categories and search_products are clearly different, so an agent can route without opening the schema, 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?

Implies the use case (look up brands, including by alias/group name) but gives no when-not-to-use guidance and never says to prefer search_products when the goal is products rather than brands. Usage is inferable but not spelled out.

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