Skip to main content
Glama

check_jp_travel_compliance

【有料 / 30 JPY】旅行者の購入額・荷物寸法・旅行日を指定し、日本の法規制適合性(新免税対象可否・特大荷物事前予約義務・祝日混雑リスク)を即決自動判定します。AIお小遣い月額上限ロック連動(1回30円、sk_souon_...必須)。 / Instant automated compliance evaluation for Japan inbound travel regulations: tax-free shopping eligibility (Nov 2026 reform), Shinkansen oversized baggage rules, or peak holiday congestion risk. 30 JPY per check, requires AI allowance API key.

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": {
      "checkType": "<checkType>"
    },
    "name": "check_jp_travel_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoAIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported.
checkTypeYes判定種別 ('tax_free', 'shinkansen_baggage', 'holiday_peak') / Compliance check type: 'tax_free', 'shinkansen_baggage', or 'holiday_peak'
travelDateNo旅行日 (YYYY-MM-DD。checkType === 'holiday_peak' で使用) / Travel date in YYYY-MM-DD format (for holiday_peak check)
baggageTotalCmNo荷物3辺合計(cm。checkType === 'shinkansen_baggage' で使用) / Total baggage dimensions in cm (length + width + height) (for shinkansen_baggage check)
purchaseAmountJpyNo購入金額(税抜日本円。checkType === 'tax_free' で使用) / Purchase amount in JPY excluding tax (for tax_free check)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two materially important traits: a per-call charge of 30 JPY and a required AI allowance API key (sk_souon_...), plus a monthly allowance-cap lock. It does not describe what a successful verdict looks like, what happens on an invalid key or insufficient allowance, or whether retries are re-charged, which are significant gaps for a paid evaluation endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded with cost and capability, which is good, but it is essentially the same paragraph duplicated in Japanese and English, and the Japanese half carries untranslated jargon (AIお小遣い月額上限ロック連動) that the English side only partially mirrors. Roughly half the text is redundant across the two languages.

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 five-parameter paid tool with no output schema, the definition should say something about the shape of the returned verdict (eligible/not eligible, risk level, required reservation flag) and error conditions on billing. It covers inputs, price, and auth but leaves the return contract entirely unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already spells out the conditional mapping (travelDate for holiday_peak, baggageTotalCm for shinkansen_baggage, purchaseAmountJpy for tax_free), so the baseline is 3. The description adds the framing that these are the traveler purchase/dimension/date inputs feeding an automatic determination, which gives mild extra meaning beyond the field text. Without an output schema, however, it cannot clarify what the returned verdict per checkType contains.

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?

The description uses a specific verb and resource: it performs an 'instant automated compliance evaluation' of Japanese inbound travel regulations, and enumerates the three concrete judgements (tax-free eligibility under the Nov 2026 reform, Shinkansen oversized baggage, holiday congestion risk). That distinguishes it from the lookup-oriented siblings list_jp_rule_categories and query_jp_inbound_rules, though the differentiation is implicit rather than stated.

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 only implied by the inputs it names (purchase amount, baggage dimensions, travel date), which suggests 'call this when you want a verdict rather than raw rules'. There is no explicit when-to-use versus when-not, and the sibling tools are never named as alternatives for rule lookups.

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.