Skip to main content
Glama

query_jp_inbound_rules

【無料 / Free 0 JPY】日本のインバウンド旅行・越境規制ルール(2026年11月改正新免税制度、JR新幹線特大荷物、祝日大型連休混雑、税関検疫)をカテゴリ・キーワードで英語検索します。APIキー不要・課金0円。 / Query official Japan inbound travel and cross-border regulatory rules in structured English JSON (tax-free reform Nov 2026, Shinkansen luggage limits, peak holiday crowding, customs/quarantine). Free, no API key required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_jp_inbound_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo取得最大件数(デフォルト: 10) / Maximum number of rules to return (default: 10)
apiKeyNoオプションのAIお小遣いキー(本ツールは無料のため渡されても課金されません) / Optional AI allowance API key (query is free, no charge even if provided).
keywordNo検索キーワード / Keyword to search across rules, facts, or summaries
categoryNoルールカテゴリ ('tax_free', 'rail_luggage', 'holidays', 'customs') / Rule category filter ('tax_free', 'rail_luggage', 'holidays', or 'customs')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"AIお小遣いキー / AI allowance API key (sk_souon_...). Authorization Bearer header also supported."New value: +"オプションのAIお小遣いキー(本ツールは無料のため渡されても課金されません) / Optional AI allowance API key (query is free, no charge even if provided)."
  2. 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 behavioral burden, and it does disclose two genuinely useful facts: no API key is required and there is zero cost/charge. However, it says nothing about result limits, pagination, data freshness/coverage boundaries, or what happens when no rules match, and 'structured English JSON' is too vague to describe the actual payload shape.

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?

The intent, coverage, and cost/auth caveats are front-loaded in the first clause, which is good. The main inefficiency is full bilingual duplication of every sentence, which roughly doubles length without adding information for an English-only agent.

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 four-optional-parameter read-only search with no output schema, an agent still needs to know the response shape (fields per rule, source attribution, whether limit truncates silently). The description claims 'structured English JSON' but does not characterize it, leaving a real gap given there is no output schema to fall back on.

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 four parameters (limit, apiKey, keyword, category) are already fully documented with bilingual descriptions and category values. The prose adds no extra meaning beyond what the schema states; it only re-mentions searching by category and keyword, so the baseline 3 applies.

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 (query) and resource (official Japan inbound travel and cross-border regulatory rules) and enumerates the covered topics: tax-free reform, Shinkansen oversized luggage, holiday crowding, customs/quarantine. It is clear what the tool returns (structured English JSON), but it never contrasts itself with siblings such as check_jp_travel_compliance or list_jp_rule_categories, so boundary clarity 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'by category/keyword' and by the enumerated topics, which hint at how to search. There is no explicit when-to-use, when-not-to-use, or routing to the sibling compliance-check or category-list tools, so an agent must guess whether this is the right entry point.

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.