Skip to main content
Glama
amazon-hikaku MCP Server

amazon-hikaku MCP Server

by aegisfleet

list_categories

Read-onlyIdempotent

Returns the parent-to-child category hierarchy with item counts per child category, so you can choose a relevant category before searching or comparing products.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the useful fact that listing counts are included in the response, but it says nothing about pagination, depth limits, ordering, or whether counts are live versus cached. With no output schema, that leaves part of the behavioral burden unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the most important information: the hierarchy structure, followed by the count metric. There is no filler, hedging, or redundant restatement of the tool name.

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?

Because there is no output schema, the description is the only source of return-value information, and it does specify both the hierarchy and the per-child counts. However, it omits whether the response is nested or flat, how deep the hierarchy goes, and how the counts are scoped, which matters for an agent that must plan around this payload. That makes it adequate but incomplete for a no-parameter, no-output-schema tool.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly does not invent parameters and instead spends its text on the return shape.

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 and resource: it returns the parent→child category hierarchy together with per-child listing counts. The required shape of the payload is clear enough to distinguish it from sibling tools such as list_brands or search_products, 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?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisite is stated. Usage is only implied: with zero parameters and a taxonomy-plus-counts payload, an agent can infer this is a browsing/entry-point tool, but nothing in the text confirms that or points to alternatives.

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