Skip to main content
Glama

tax_free_guide

Read-onlyIdempotent

Get Japan tax-free shopping rules for tourists, including the November 1, 2026 refund system, airport refund steps, store fees, and common mistakes with links to guides.

Instructions

Japan tax-free shopping rules for tourists (refund system since November 1, 2026) with links to detailed guides: airport refunds, refund fees by store and common mistakes.

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": "tax_free_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and side-effect profile are covered. The description adds that the content is a rules summary with links to detailed guides, but says nothing about how results are returned or whether links are external resources.

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?

One compact sentence with the topic front-loaded and supporting detail after the colon; no wasted prose. The trailing list of link topics is slightly loose but still earns its place by signaling coverage.

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 simple one-parameter, no-output-schema informational tool, the description conveys the subject matter adequately. It does not clarify the return shape (prose versus a list of links) or the effect of the language parameter, which leaves small but real gaps.

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

Parameters2/5

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

The single parameter (language, default 'en') has 0% schema description coverage and is never mentioned in the description. An agent must infer that language controls the guide's output language and that 'en' is the fallback, so the description adds essentially no meaning beyond the schema.

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 names a specific resource (Japan tax-free shopping rules for tourists) and scopes it to the post-November 1, 2026 refund system, so an agent can tell it is an informational guide rather than a coupon or price tool. It lacks an explicit action verb (does it return text, links, or a summary?), which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is only implied by the tourist/tax-refund framing, leaving the agent to infer that this is for informational queries about Japanese tax refunds.

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