Skip to main content
Glama

Jp Tariff Search

jp_tariff_search
Read-onlyIdempotent

Search Japan's customs tariff schedule by product keyword (English) and get the matching HS lines with their headline duty rates (general, WTO, GSP, LDC). Use it to find which HS code and duty rate Japan applies to a product such as beans, green tea, lithium batteries, wine or cotton fabric, then call jp_tariff_lookup for every partnership rate. Optional chapter (1-97) limits the search to one HS chapter. Returns the schedule edition date; no match returns found:false with a hint.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chapter": 7,
      "keyword": "adzuki beans"
    },
    "name": "jp_tariff_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches (default 10, max 30).
chapterNoOptional HS chapter 1-97 to search within (rates then come from that chapter live).
keywordYesProduct words in English, e.g. "adzuki beans", "green tea", "lithium battery". All words must appear.

Output Schema

NameRequiredDescriptionDefault
hintNo
foundNo
sourceNo
keywordNo
resultsNo
returnedNo
searchedNo
data_as_ofNo
match_modeNo
attributionNo
match_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the response carries the schedule edition date, and a no-match returns found:false with a hint, which tells the agent how to detect and recover from empty results. It stops short of describing match ranking or rate freshness beyond the edition date.

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?

Three sentences, front-loaded with the action and its output, followed by routing guidance and edge-case behavior. Every clause carries information; nothing is padding.

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

Completeness5/5

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

An output schema exists, so return structure need not be spelled out, yet the description still flags the edition-date field and the found:false no-match case. Combined with explicit sibling routing and chapter scoping, an agent has everything needed to call it correctly.

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 coverage is 100% and the schema already documents keyword language, the all-words-must-appear rule, chapter range and limit defaults. The description mostly restates those, adding only the framing that chapter scoping also affects where rates come from — a modest increment over structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — search Japan's customs tariff schedule by English product keyword — and names the exact return content (HS lines with headline general/WTO/GSP/LDC duty rates). It also distinguishes itself from jp_tariff_lookup, which handles partnership rates, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use this to find the HS code and headline duty rate, then call jp_tariff_lookup for every partnership rate. Concrete example products (beans, green tea, lithium batteries, wine, cotton fabric) anchor the use case, and no exclusion is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.