Skip to main content
Glama
Sign In

KH Merch Graph

by io.github.marleyhereicome-cpu
OverviewDiscussionsAdmin

Estimate cost to ship from Japan

estimate_landed_cost
Read-onlyIdempotent

Estimate the total cost of buying an item in Japan and having it forwarded abroad. Example: {price_jpy: 4500, sku_id: "ichiban-kuji-kh-2018-a", dest_country: "US"}. Returns routes[] (forwarding service × shipping method, with fees and total_jpy, cheapest first) and cheapest. Rough figures only: fee and shipping tables currently cover US, GB, DE and FR (other countries return no routes), come from third-party comparison guides (mid-2026) and exclude duties. Not a quote; we are not affiliated with any forwarding service.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "price_jpy": "<price_jpy>",
      "dest_country": "<dest_country>"
    },
    "name": "estimate_landed_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxyNoOnly show one forwarding service, e.g. "buyee". Optional.
sku_idNoCatalog sku_id, used to look up the weight. Optional.
weight_gNoPackage weight in grams, when there is no sku_id or the catalog has no weight.
price_jpyYesItem price in Japanese yen (required).
dest_countryYesDestination country as an ISO 3166-1 alpha-2 code, e.g. "US", "GB", "AU".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / dest_country / description
      Previous value: -"仕向国（ISO2、例: US）"New value: +"Destination country as an ISO 3166-1 alpha-2 code, e.g. \"US\", \"GB\", \"AU\"."
    • changedInput schema / properties / price_jpy / description
      Previous value: -"出品価格（円、必須）"New value: +"Item price in Japanese yen (required)."
    • changedInput schema / properties / proxy / description
      Previous value: -"代行名を指定して絞り込む（任意）"New value: +"Only show one forwarding service, e.g. \"buyee\". Optional."
    • changedInput schema / properties / sku_id / description
      Previous value: -"正規SKU_ID（重量の参照に使用、任意）"New value: +"Catalog sku_id, used to look up the weight. Optional."
    • changedInput schema / properties / weight_g / description
      Previous value: -"重量（g、sku_idが無い場合はこちらを指定）"New value: +"Package weight in grams, when there is no sku_id or the catalog has no weight."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses substantive behavior: coverage limited to four countries, data sourced from third-party comparison guides mid-2026, duties excluded, 'rough figures only', and an explicit disclaimer that it is not a quote and there is no affiliation with any forwarder. That is exactly the context annotations cannot carry.

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-loaded with purpose, then an example, then return shape, then caveats — a sensible order with no filler sentences. Dense but every clause (coverage limits, exclusions, disclaimers) carries real information.

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?

With no output schema, the description usefully describes routes[] (forwarding service × shipping method, fees, total_jpy, cheapest-first) and cheapest. The one unaddressed case is what happens when neither sku_id nor weight_g is supplied, which the required-parameter list does not resolve.

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 100%, so the baseline is 3. The inline example reinforces price_jpy, sku_id and dest_country usage and the sku-to-weight lookup, but proxy and weight_g are not elaborated beyond the schema, so it adds no meaning the schema lacks.

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: 'Estimate the total cost of buying an item in Japan and having it forwarded abroad,' which is unmistakably distinct from discover, explain_product, or resolve_listing. It never names a sibling, but the purpose is so narrow that confusion is unlikely.

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 clear context for use: item price plus destination, an inline example call, and an explicit exclusion ('other countries return no routes' beyond US, GB, DE and FR). It stops short of pointing to an alternative tool when the country is unsupported, so a 5 isn't warranted.

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

All KH Merch Graph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources