Skip to main content
Glama

Tax Compass — Japan tax rules by date

インボイスの消費税の端数(税率ごとに1回)

jp_invoice_consumption_tax
Read-onlyIdempotent

Calculate Japanese consumption tax on a qualified invoice (適格請求書 / インボイス) the way Japan's National Tax Agency requires: sum the lines per tax rate (10% standard, 8% reduced, and 1% for food sold 2027-04-01 to 2029-03-31 — that 1% rate is still a bill in the Diet, so give each 1% line its transaction date and the answer marks it rule_status bill), then round the tax ONCE per rate per invoice — never per line. It applies to writing, checking or explaining a Japanese invoice, receipt (適格簡易請求書) or delivery note total (納品書), and to questions about why per-item tax (消費税 端数処理) adds up differently. It calculates one invoice from a single issuer; when one document carries invoices of several businesses, the agency-delivery case (代理交付) must be rounded per business and per rate. Rounding direction (切り捨て floor / 四捨五入 round_half_up / 切り上げ ceil) is the issuer's choice. All lines of one invoice must use the same price basis (税抜 or 税込). Returns per-rate totals, the correct tax, and what per-line rounding would have given, with NTA sources. It does not check other invoice requirements such as the registration number.

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": {
      "price_basis": "<price_basis>",
      "rounding": "<rounding>",
      "lines": "<lines>"
    },
    "name": "jp_invoice_consumption_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
roundingYes1円未満の処理。切り捨て・四捨五入・切り上げ
price_basisYes行の金額が税抜(tax_excluded)か税込(tax_included)か。1枚の中ではどちらかに揃える
transaction_dateNo取引(譲渡)の日 YYYY-MM-DD。行に date が無い時に使う。税率 1 の行には、どちらかの日が要る

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.8/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, and the description adds real behavioral context on top: the 1% rate is provisional legislation so lines get flagged rule_status=bill, 1% lines need a transaction date, all lines of one invoice must share a price basis, and the response includes both the correct tax and the per-line-rounding comparison with NTA sources. Those are non-obvious constraints and output behaviors an agent could not infer 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.

Conciseness4/5

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

The core action and the round-once-per-rate rule are front-loaded, and nearly every clause carries decision-relevant content. It is dense, however — long multi-clause sentences with embedded parentheticals (the 1% bill-in-the-Diet caveat sits mid-sentence) make it slower to parse than a few shorter sentences would.

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?

An output schema exists, yet the description still summarizes what comes back (per-rate totals, correct tax, per-line comparison, sources), and it covers the tricky cases — provisional 1% rate, mixed rates, 代理交付, tax-included vs tax-excluded — that determine whether a call is valid. Nothing needed to call it correctly is missing.

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 75% and the Japanese field descriptions are already detailed, but the description still adds decision-relevant meaning: rounding direction is the issuer's choice rather than a fixed rule, price_basis must be uniform within one invoice, and the date requirement applies specifically to 1% lines. It stops short of covering the discount sign convention or amount bounds, which the schema handles.

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 gives a specific verb and resource — calculating consumption tax on a qualified invoice — and pins the distinctive behavior (round once per tax rate per invoice, never per line). It scopes in receipts, delivery notes, and 'why per-item tax adds up differently' questions, and scopes out other invoice checks like registration numbers, which is enough to separate it from the rate/amount siblings without naming them.

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

Usage Guidelines5/5

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

It explicitly lists when to use it (writing, checking, or explaining an invoice, 適格簡易請求書, 納品書, or per-line vs per-rate rounding questions) and when not to (multi-business 代理交付 documents must be rounded per business and per rate; other invoice requirements are out of scope). An agent has a clear routing rule and an explicit exclusion.

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