Skip to main content
Glama

jimu (renamed to Tax Compass)

請求書の金額(小計・消費税・源泉徴収・振込額・支払期日)

jp_invoice_amount
Read-onlyIdempotent

Work out the amounts on a Japanese invoice in one call by combining the other Tax Compass calculations: subtotal, consumption tax rounded once per tax rate (国税庁 Q&A 問57), withholding tax on item-1 fees paid to a resident individual (No.2795; on the tax-excluded fee when the consumption tax (or its equivalent) is stated separately on the invoice, which the NTA allows also for issuers not registered for the invoice system; otherwise on the tax-included amount), the transfer amount (振込額), the payment due dates under 取適法 if terms are given, and a check of numbers already written on the invoice. For an issuer not registered for the invoice system (免税事業者) it adds the NTA Q&A 問26-2 notes on what such an invoice may and may not show. Whether a fee is subject to withholding and which tax rate applies are chosen by the caller.

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>",
      "issuer_registered": "<issuer_registered>"
    },
    "name": "jp_invoice_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
statedNo請求書に書いた数(検算する時。書いてある物だけ入れる)
roundingYes1円未満の処理。切り捨て・四捨五入・切り上げ
price_basisYes行の金額が税抜(tax_excluded)か税込(tax_included)か。1枚の中ではどちらかに揃える
withholdingNo日本に住む個人に払う第1号の報酬として源泉徴収する時だけ入れる
payment_termsNo支払期日もまとめて出す時(jp_payment_due_date と同じ入力)
transaction_dateNo取引(譲渡)の日 YYYY-MM-DD。行に date が無い時に使う。税率 1 の行には、どちらかの日が要る
issuer_registeredYes請求書を出す人が適格請求書発行事業者(インボイスの登録をしている)か

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. Changed9 schema fields changed
    • addedInput schema / properties / lines / items / properties / date
      Added value: +{
      +  "description": "この行の取引(譲渡)の日 YYYY-MM-DD(8% と 1% が混ざる請求書の時など)",
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • changedInput schema / properties / lines / items / properties / rate / description
      Previous value: -"税率(%)。8 は軽減税率。どちらの税率かは呼ぶ側(利用者)が選ぶ"New value: +"税率(%)。8 は軽減税率。1 は 2027-04-01〜2029-03-31 の飲食料品の税率で、まだ法案(成立していない)。どの税率かは呼ぶ側(利用者)が選ぶ"
    • changedInput schema / properties / lines / items / properties / rate / enum
      Previous value: -[
      -  "8",
      -  "10"
      -]New value: +[
      +  "1",
      +  "8",
      +  "10"
      +]
    • addedInput schema / properties / transaction_date
      Added value: +{
      +  "description": "取引(譲渡)の日 YYYY-MM-DD。行に date が無い時に使う。税率 1 の行には、どちらかの日が要る",
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / contains_bill_rate
      Added value: +{
      +  "description": "法案の段階の税率(1%)を使った行があるか。true なら金額は確定していない",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / properties / if_bill_not_enacted
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "consumption_tax": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "total_tax_included": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "consumption_tax",
      +        "total_tax_included"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "1% の行があった時、法案が成立しない場合(1% の行を 8% にした時)の合計。1% の行が無ければ null"
      +}
    • addedOutput schema / properties / result / properties / per_rate / items / properties / rule_status
      Added value: +{
      +  "description": "その税率の決まりの状態。1 は法案の間 bill(確定していない)",
      +  "enum": [
      +    "in_force",
      +    "enacted",
      +    "bill",
      +    "planned"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / result / properties / per_rate / items / required
      Previous value: -[
      -  "rate",
      -  "total_tax_excluded",
      -  "consumption_tax",
      -  "total_tax_included"
      -]New value: +[
      +  "rate",
      +  "total_tax_excluded",
      +  "consumption_tax",
      +  "total_tax_included",
      +  "rule_status"
      +]
    • changedOutput schema / properties / result / required
      Previous value: -[
      -  "per_rate",
      -  "subtotal_tax_excluded",
      -  "consumption_tax",
      -  "total_tax_included",
      -  "withholding",
      -  "transfer_amount",
      -  "check",
      -  "payment_due"
      -]New value: +[
      +  "per_rate",
      +  "contains_bill_rate",
      +  "if_bill_not_enacted",
      +  "subtotal_tax_excluded",
      +  "consumption_tax",
      +  "total_tax_included",
      +  "withholding",
      +  "transfer_amount",
      +  "check",
      +  "payment_due"
      +]
  2. 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 the tool read-only, idempotent, closed-world, and non-destructive, and the description adds substantive computation behavior: rounding once per tax rate, the withholding base depending on whether consumption tax is separately stated, and special notes for unregistered issuers. It does not discuss error handling, but the output schema covers return values.

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 free of filler, but the first sentence is a long run-on with nested parentheticals and legal citations, making it harder to scan than necessary. The length is justified by the tool's complexity, though a more structured presentation would improve readability.

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?

For a complex, multi-calculation invoice tool with an output schema and rich annotations, the description covers the key outputs, rounding rule, withholding treatment, payment due date handling, and the unregistered-issuer caveat. Nothing essential for correct invocation is missing, especially since the input schema documents the parameters in detail.

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 high at 88%, so the baseline is 3; the description goes further by explaining withholding conditions, the tax-excluded versus tax-included withholding base, and the significance of issuer registration. It does not add meaning for every parameter, but it gives useful domain context for the most consequential ones.

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 and resource ('Work out the amounts on a Japanese invoice') and enumerates the exact outputs: subtotal, consumption tax, withholding tax, transfer amount, payment due dates, and an invoice-number check. It also positions the tool as a one-call combination of the other Tax Compass calculations, distinguishing it from individual sibling calculators.

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 establishes a clear use case: producing the full set of invoice amounts in one call, with payment due dates only when terms are supplied and withholding only for item-1 fees paid to a resident individual. It does not explicitly state when to use a sibling calculator instead, so it stops short of full when/when-not guidance.

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