Skip to main content
Glama

Jp Tariff Lookup

jp_tariff_lookup
Read-onlyIdempotent

Look up Japan's applied customs tariff rates by HS code: the line description and the general, temporary, WTO, GSP and LDC duty rates, the rate under each economic partnership agreement (CPTPP, EU, UK, RCEP, ASEAN, Australia, India, Switzerland and others, plus the JP-US trade agreement) and the quantity units. Accepts a 2-digit chapter, 4-digit heading (e.g. 0713 dried legumes), 6-digit subheading or 9-digit statistical code, with or without dots; a longer foreign code is cut to its first 6 digits. Answers 'what duty does Japan charge on this HS code', 'Japan import tariff on X', 'Japan EPA preferential rate for Y'. Returns the schedule edition date; an unknown code returns found:false.

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": {
      "hs_code": "0713"
    },
    "name": "jp_tariff_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum lines to return (default 25, max 100).
hs_codeYesHS code, 2 to 9 digits, dots optional (e.g. "0713", "0713.32", "071332010"). Codes longer than 9 digits are cut to 6.
partnerNoOptional trade-agreement partner to keep in epa_rates, e.g. "cptpp", "eu", "uk", "india", "rcep", "viet_nam", "australia".

Output Schema

NameRequiredDescriptionDefault
foundNo
linesNo
sourceNo
headingNo
hs_codeNo
returnedNo
truncatedNo
data_as_ofNo
line_countNo
rate_notesNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description goes further by disclosing normalization behavior (dots optional, foreign codes truncated to 6 digits) and the failure mode ('an unknown code returns found:false'), which the annotations cannot express.

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?

Front-loads the resource and payload, then normalizes input rules, then example questions — a logical order with no filler sentences. The dense list of agreements (CPTPP, EU, UK, RCEP, ASEAN, Australia, India, Switzerland) is long but informative rather than redundant.

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?

An output schema exists, so return shape needn't be spelled out, yet the description still states the edition date and the found:false case, covering the two things an agent must handle. Input normalization and coverage scope are complete for a read-only lookup tool.

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%, so all three parameters are already documented, which sets the baseline at 3. The description reinforces the accepted code formats and truncation rule and names the partner agreements, but adds little about 'limit' or partner-filter semantics beyond what the schema says.

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?

Opens with a specific verb and resource ('Look up Japan's applied customs tariff rates by HS code') and enumerates exactly what is returned (line description, general/temporary/WTO/GSP/LDC rates, EPA rates, quantity units). It never names the sibling jp_tariff_search, so the boundary between a 'lookup' and a 'search' is left to inference.

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?

Gives concrete user-question framings ('what duty does Japan charge on this HS code', 'Japan EPA preferential rate for Y') that tell the agent when this tool is the right call. There is no when-not guidance and no mention of alternatives such as jp_tariff_search, so the routing logic is only implied.

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.