Skip to main content
Glama

Korea Import Customs Duty & Cross-Border Payout MCP

Calculate South Korea Import Customs Duty & Landed Cost

calculate_korea_import_customs
Read-onlyIdempotent

Calculates Korean import customs duty, VAT, and total landed KRW cost for overseas direct purchases (USD, JPY, EUR, CNY) vs domestic Coupang Rocket delivery.

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": {
      "keyword": "<keyword>",
      "price": "<price>"
    },
    "name": "calculate_korea_import_customs"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesOverseas item price in selected currency
countryNoOrigin country code: US ($200 duty-free), CN, JP, EU ($150 duty-free)
keywordYesProduct name in Korean or English (e.g. '맥미니 M4', 'RTX 5070', '로봇청소기')
categoryNoOne of: pc_parts, electronics, supplements, sports_golf, fashion_camping
currencyNoCurrency code: USD, JPY, EUR, CNY
domestic_krwNoDomestic Korean retail price in KRW for break-even comparison
forwarder_krwNoInternational shipping/forwarding fee in KRW (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that duties, VAT, and landed cost are computed and that a break-even comparison is produced, but omits key behavioral caveats: whether results are estimates, what duty/VAT rates or thresholds are assumed, and whether the response is a breakdown or a single total (no output schema exists).

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?

A single dense sentence with the primary function front-loaded and no filler. It is slightly overloaded by parenthetical currency lists, but nothing is wasted.

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 seven-parameter domain calculation with no output schema, the description covers purpose but not the shape of results (duty vs VAT vs total breakdown) or rate assumptions. The schema compensates for inputs, but the agent lacks behavioral context needed to interpret and trust the output.

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 all seven parameters are already documented, including duty-free thresholds. The description's currency list (USD, JPY, EUR, CNY) merely repeats schema content and adds no new meaning about how price, country, or domestic_krw interact.

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 ('Calculates') and precise resources (Korean import customs duty, VAT, total landed KRW cost), plus the currency scope and the comparison target ('domestic Coupang Rocket delivery'). An agent can tell this apart from a payout-fee tool without opening the schema.

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?

Usage is implied by the description ('overseas direct purchases... vs domestic Coupang Rocket delivery'), so an agent can infer a cross-border purchase comparison scenario. However, it never states when to use this versus the sibling compare_crossborder_payout_fees, nor any prerequisites such as needing a domestic price for the break-even comparison.

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.