Skip to main content
Glama

jimu (renamed to Tax Compass)

所得税の基礎控除と「年収の壁」(年分ごと・令和7〜12年分)

jp_tax_basic_deduction
Read-onlyIdempotent

Japanese income tax basic deduction (基礎控除) for a given year (年分, 2025–2030), with the table by total income (合計所得金額) and, optionally, the deduction for one total income. The 2026 tax reform (enacted 2026-03-31, in force 2026-12-01) raised it: for 2026 and 2027 it is ¥1,040,000 up to ¥4.89 million of total income, ¥670,000 up to ¥6.55 million, ¥620,000 up to ¥23.5 million, then 480k/320k/160k/0; from 2028 it is ¥990,000 up to ¥1.32 million and ¥620,000 above. 2025 is the earlier table (95/88/68/63/58万円). Also returns the minimum employment income deduction (給与所得控除の最低保障: 65万 / 74万 / 69万) and the income line for dependants (扶養親族の所得要件 58万 → 62万), and the salary-only income tax line (年収の壁 160万 → 178万 → 168万円). The extra amount on top of ¥620,000 applies to residents only. Income tax only — not resident tax or social insurance.

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_tax_basic_deduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo年分(西暦 2025〜2030)。例:令和8年分=2026。省くと as_of の年
as_ofNoyear を省く時の日 YYYY-MM-DD(その年分)。両方省くと今日(日本時間)
residentNo居住者か(省くと true)。非居住者は上乗せ(措法41の16の2)が無い
total_incomeNo合計所得金額(円)。年収(収入)ではない。入れるとその人の基礎控除の額を返す

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. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered; the description goes well beyond that by disclosing the legal source and timing of the change (enacted 2026-03-31, in force 2026-12-01), the exact amounts that shift per year band, and that the amount above ¥620,000 applies to residents only. It also warns that the input is 合計所得金額, not 年収, which prevents a common misuse.

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 purpose is front-loaded and there is no filler prose, but the middle section enumerates the entire deduction table (104/67/62/48/32/16/0万円, 95/88/68/63/58万円, 65/74/69万, 58→62万, 160→178→168万). Since an output schema exists and the tool itself returns these figures, the enumeration is largely redundant bulk that makes the sentence hard to parse.

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

Completeness4/5

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

Given an output schema covering return values and full schema coverage on all four optional parameters, the description supplies what is actually needed: domain scope, effective dates, year-to-table mapping, and explicit exclusions. It does not explain defaulting behavior (omitting year falls back to as_of/today) itself, but the schema carries that, leaving only a minor gap.

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%, and the schema already documents the 2025–2030 bounds, the 合計所得金額-vs-年収 distinction, and the 非居住者 caveat (措法41の16の2). The description's parameter-relevant content — year range, resident-only extra, income figure — largely restates the schema, so this sits at the baseline rather than adding new meaning.

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?

The description opens with a specific verb+resource: it returns the Japanese income tax basic deduction (基礎控除) for a given 年分, with the table by 合計所得金額 and optionally a single person's amount. It also scopes itself explicitly against adjacent domains ('Income tax only — not resident tax or social insurance'), which distinguishes it from siblings such as jp_tax_consumption_rate or jp_withholding_tax_fees.

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?

It states the condition for the optional mode ('optionally, the deduction for one total income'), which maps to when to pass total_income, and it names an explicit exclusion (no resident tax, no social insurance). What is missing is any routing to sibling tools or guidance on which year values map to which reform table when a caller is unsure.

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