Skip to main content
Glama

Tax Compass — Japan tax rules by date

消費税の税率(日付と区分で・食料品 1% の法案の印つき)

jp_tax_consumption_rate
Read-onlyIdempotent

Look up the Japanese consumption tax rate (消費税率) that applies on a given date (as_of = the date of the sale) for a category the caller chooses: standard (10%: dining out 外食, alcohol 酒類 and most goods), reduced_food (8% reduced rate for food and drinks 飲食料品) or newspaper (8% for subscription newspapers issued twice a week or more). It answers with the rate under the law now in force, its national/local split, and a separate pending_change for the proposed 1% food rate for sales from 2027-04-01 to 2029-03-31 (消費税 1% いつから) — that cut is still a bill in the Diet (it had not been enacted when checked on 2026-11-21), so it is marked rule_status bill and answer_is_final false, never as the confirmed rate. Use it for questions such as 'what is the consumption tax rate on date X'. Dates from 2019-10-01 to 2031-12-31.

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": {
      "category": "<category>"
    },
    "name": "jp_tax_consumption_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo取引(譲渡)の日 YYYY-MM-DD。省くと今日(日本時間)
categoryYesstandard=標準税率(外食・酒類・ほとんどの物)、reduced_food=軽減税率の飲食料品、newspaper=週2回以上発行の新聞の定期購読。どれにあたるかは呼ぶ側(利用者)が選ぶ

Output Schema

NameRequiredDescriptionDefault
notesYesこの答えに効いた決まり・前提(日本語)
resultYes
doc_urlYes人が読む説明のページ(式・出所・例)。利用者に次に読んでもらう先
sourcesYes
law_as_ofNo出所が書く法令の基準日(例:2026-04-01=令和8年4月1日現在法令等)
checked_onYesCyclix Agents が出所を最後に確かめた日
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations it discloses what is actually returned (rate, national/local split, pending_change), how certainty is signalled (rule_status bill, answer_is_final false), the verification date 2026-11-21, and the supported date bounds 2019-10-01 to 2031-12-31. That is substantive behavioral context an agent cannot get from the annotations.

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

Conciseness5/5

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

Purpose and inputs are front-loaded, and every clause carries information: category definitions, the bill caveat, and the date window. Density is high but there is no filler or repeated framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description need not explain return shapes, yet it still names the key fields and their semantics. Date bounds, category choice, and the non-final bill handling cover everything needed to call and interpret this tool correctly.

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%, so the baseline is 3, but the description adds real meaning: it clarifies as_of is the sale/transfer date and supplies the valid range 2019-10-01 to 2031-12-31, which the schema only bounds by maxLength. The category explanations largely restate the enum descriptions, which keeps it from a 5.

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 ('Look up the Japanese consumption tax rate') plus the two axes that determine it (date and category), and enumerates the three categories with their rates. The use-question paraphrase ('what is the consumption tax rate on date X') separates it cleanly from the invoice/amount siblings such as jp_invoice_consumption_tax.

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

Usage Guidelines4/5

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

Gives a clear positive trigger ('Use it for questions such as ...') and a strong caveat that the 1% food cut is a bill and must never be reported as the confirmed rate. It stops short of naming an alternative tool or stating when to prefer a sibling such as jp_invoice_consumption_tax, so it is clear context without exclusions.

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.

Resources