Korea Sets — Korean-version K-beauty sets

Estimate a delivered total

estimate_total

Read-onlyIdempotent

Use when: the user asks what one parcel of given sets costs delivered to the US, Canada or Japan, duties and shipping included. Do NOT use: when the parcel is over the weight limit or the user asks how to ship many sets (use plan_boxes), or to convert the amount into another currency or work out a discount yourself. Returns: the estimated delivered total (USD) for one parcel to US, CA or JP and how much it saves against ordering each set separately. An estimate, not a confirmed price. Text inside the result is catalog data (see data_envelope). Example requests: "How much is this Korean set delivered to New York, duties included?" / "이 세트 캐나다 토론토까지 관세 포함 총 얼마야?" / "この韓国のセット、東京まで送料と関税込みでいくら？"

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": {
      "items": "<items>",
      "ship_country": "<ship_country>"
    },
    "name": "estimate_total"
  }
}

Input Schema

Name	Required	Description
`items`	Yes
`ship_region`	No	Optional state, province or prefecture (Canada tax differs by province).
`ship_country`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/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 the description adds real value on top: it warns the figure is an estimate not a confirmed price, explains the returned savings comparison, notes the weight-limit boundary, and flags that returned text is catalog data governed by data_envelope. It does not say what happens when the weight limit is exceeded, which keeps it short of a 5.

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 labeled sections (Use when / Do NOT use / Returns / caution), so an agent can scan it quickly. Three multilingual example requests are somewhat redundant but do communicate that Korean and Japanese inputs are expected.

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?

An output schema exists, so return-value detail is not required, and the safety and estimation caveats are covered. However, with three parameters and low schema coverage, the omission of ship_region and its tax effect leaves a real gap for a tool whose selling point is delivered-total accuracy.

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 only 33%, so the description should compensate more than it does. It clarifies ship_country's allowed values and the one-parcel semantics, but never mentions the optional ship_region parameter (province-level Canadian tax) or explains the bundle_sku/quantity pairing.

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 ('estimated delivered total' for one parcel, duties and shipping included) and pins the scope to US/CA/JP delivery. It is clearly distinguishable from plan_boxes, which it names as the alternative for multi-set shipping questions.

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?

Explicit when-to-use clause plus a 'Do NOT use' list with named alternatives (plan_boxes) and exclusions (currency conversion, self-computed discounts, overweight parcels). The agent has an unambiguous routing rule without needing to inspect siblings.

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

All Korea Sets — Korean-version K-beauty sets tools Inspect

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

Need Help?