Skip to main content
Glama

Tax Compass — Japan tax rules by date

これから変わる日本の決まり(改正カレンダー・日付順)

jp_rules_changes
Read-onlyIdempotent

Upcoming (and in-progress) changes to Japanese business rules in date order — consumption tax (the proposed 1% food rate, still a bill), invoice transitional credit steps (80→70→50→30→0%), the 2割/3割 special rules, income tax basic deduction, withholding tables, the defense special income tax, minimum wage, employment insurance rates, the child-support levy, the working-pension threshold and the departure tax. Each item has effective dates, a status (in_force / enacted / bill / planned) computed against today, a one-line summary in Japanese, the official source URL and the date Cyclix Agents checked it, and the Tax Compass tool that calculates it if there is one. Filter by as_of (list items that start on or after it, or are still in effect on it — a change with no end date stays in effect), until, areas and statuses. Only items whose numbers were checked against the official source are listed; it is not a complete list of all law changes.

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

Input Schema

NameRequiredDescriptionDefault
areasNo分野で絞る(省くと全部)
as_ofNoこの日以後に始まる変更と、この日に当てはまっている変更(終わりの日が無い物を含む)を出す YYYY-MM-DD。省くと今日(日本時間)
untilNoこの日までに始まる変更だけ YYYY-MM-DD(省くと全部)
statusesNo状態で絞る(省くと全部)。bill は国会で未成立

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.4/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint, idempotentHint, non-destructive), so the description's real contribution is data provenance and scope: each item carries effective dates, a status computed against today, a Japanese one-liner, source URL, and the check date, and the list is deliberately incomplete because only verified numbers appear. That is meaningful context beyond the annotations, though coverage/refresh cadence is not stated.

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?

Purpose and scope are front-loaded, then the covered topics, then the filter model and the completeness caveat. The long enumeration of tax topics is bulky but functional for query matching; a few items could be trimmed without loss.

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?

Return fields are described (effective dates, status, Japanese summary, source URL, verification date, linked calculator) and an output schema exists, so the pairing is sufficient. With annotations covering safety and schema covering parameters, an agent has everything needed to call and interpret this tool.

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; the description earns a point by spelling out the as_of semantics more operationally ('start on or after it, or are still in effect on it — a change with no end date stays in effect') and clarifying that status defaults to today in JST when omitted.

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 ('upcoming changes to Japanese business rules in date order') and enumerates the covered domains (consumption tax, invoice transitional credit, minimum wage, departure tax, etc.), which lets an agent match a user question without opening the schema. It also implicitly contrasts with the sibling calculators by noting each item links to 'the Tax Compass tool that calculates it'.

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?

Explains the filtering model (as_of, until, areas, statuses) and gives a clear exclusion: only source-verified items are listed and it is not a complete list of law changes. It does not explicitly say 'use jp_tax_consumption_rate for the current number', leaving sibling routing partly implicit.

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