Skip to main content
Glama

jimu (renamed to Tax Compass)

2割特例・3割特例の期間(課税期間が入るか)

jp_tax_small_business_special
Read-onlyIdempotent

Japanese consumption tax special rules for small businesses that became taxable because they registered for invoices: the 2割特例 (pay 20% of output tax) applies to each taxable period that contains any day from 2023-10-01 to 2026-09-30, and the new 3割特例 (pay 30% of output tax, individuals only) applies to the 2027 and 2028 calendar years. Give a date and the taxpayer type (individual = calendar year; corporation = give the business year start and end) and it says whether that taxable period is inside each window. It only checks the period; whether the other conditions are met (base-period sales of ¥10 million or less, not taxable anyway, etc.) is for the caller to decide. From the 2026 tax reform law enacted 2026-03-31 (NTA invoice Q&A 問114, 114-2).

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": {
      "taxpayer_type": "<taxpayer_type>"
    },
    "name": "jp_tax_small_business_special"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo課税期間に含まれる日 YYYY-MM-DD(2023-10-01〜2031-12-31。法人の課税期間が 2023-10-01 より前に始まる時はその初日から)。省くと今日(日本時間)
period_endNo法人の課税期間(事業年度)の末日 YYYY-MM-DD
period_startNo法人の課税期間(事業年度)の初日 YYYY-MM-DD
taxpayer_typeYesindividual=個人事業者(課税期間は暦年)、corporation=法人

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

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real value beyond that by stating the containment rule ('contains any day from 2023-10-01 to 2026-09-30'), noting the 3割特例 is individuals-only, and citing the legal source (2026 reform law, NTA 問114/114-2), which lets the agent judge currency of the rule.

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 opening sentence is long and carries the full rule text, but the scope caveat and source citation are placed deliberately and nothing is filler. A slightly tighter split between the rule summary and the usage instruction would improve scanability.

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?

An output schema exists, so return values need not be explained. Combined with annotations covering safety, the description supplies what an agent still needs: what is checked, what is explicitly not checked, and the legal basis. Only a concrete example of a straddling corporation period would add more.

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 the baseline is 3. The description restates the individual = calendar year / corporation = business-year start+end mapping, which the schema already documents, and adds little new syntax or edge-case meaning beyond that duplication.

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 names the concrete resource (2割特例 / 3割特例 windows for a taxable period) and a precise check ('says whether that taxable period is inside each window'). It is easy to distinguish from siblings such as jp_tax_invoice_transitional_credit or jp_tax_consumption_rate because the scope is a period-containment test, not a rate lookup or credit calculation.

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 clearly states the required inputs ('Give a date and the taxpayer type') and draws an explicit boundary: 'It only checks the period; whether the other conditions are met ... is for the caller to decide.' That tells the agent when this tool is sufficient and when it is not, though it never names a specific alternative sibling for the excluded eligibility questions.

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