Skip to main content
Glama

jimu (renamed to Tax Compass)

免税事業者からの仕入れの控除の割合(80%→70%→50%→30%→0)

jp_tax_invoice_transitional_credit
Read-onlyIdempotent

Japanese invoice system (インボイス) transitional measure (経過措置): how much of the deemed input consumption tax on a purchase from a tax-exempt business or a consumer (免税事業者等からの課税仕入れ) may still be credited on a given purchase date — 80% until 2026-09-30, 70% from 2026-10-01 to 2028-09-30, 50% to 2030-09-30, 30% to 2031-09-30, then 0% (2割控除・7割控除 いつから). The percentage follows the date of the purchase (services: the day the whole service is completed; goods: the day of delivery). With an optional tax-included amount it also computes the deemed creditable amount: amount × 7.8/110 (reduced rate: 6.24/108) × percent, rounded once (NTA invoice Q&A 問130). Amended by the 2026 tax reform law enacted 2026-03-31. Dates from 2023-10-01 to 2031-12-31.

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

Input Schema

NameRequiredDescriptionDefault
rateNoその仕入れの税率 %(省くと 10)。8 は軽減税率。どちらかは呼ぶ側(利用者)が選ぶ
as_ofNo課税仕入れの日 YYYY-MM-DD(役務は全部が完了した日・商品は引渡しの日)。省くと今日(日本時間)
amountNo免税事業者等に払った対価の額(税込・円)。入れると控除できる額も計算する
roundingNo1円未満の処理(省くと切り捨て)。問130 は切捨て又は四捨五入

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

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds the legal basis, transition schedule, computation formula, rounding authority, amendment status, and accepted date range. That is substantial behavioral context beyond 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 description is front-loaded and information-dense, with the date milestones immediately visible and every major sentence carrying legal or computational content. The inline bilingual parentheticals and the phrase '2割控除・7割控除 いつから' make it slightly heavier than necessary, but it is not wasteful.

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 four optional parameters, full schema descriptions, annotations, and an output schema, the description supplies the missing decision context: date scope, computation, rounding, and legal version. Nothing material is omitted for an agent to call it 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 still adds the amount formula (7.8/110 and reduced-rate 6.24/108) and ties rate 8 to the reduced rate. It repeats some of the as_of semantics already in the schema, so it is strong but not fully additive.

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 opening states a specific verb and resource: it returns the transitional credit percentage for deemed input tax on purchases from tax-exempt businesses or consumers, with explicit date bands. The scope is narrow and clearly distinct from general consumption-tax or invoice-amount siblings.

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 defines the exact scenario and dates for use, including purchase-date rules for services versus goods, and the optional amount computation. It does not name sibling alternatives or state when not to use it, so it falls short of a 5.

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