Skip to main content
Glama

jimu (renamed to Tax Compass)

印紙税はいくら?(領収書・不動産の譲渡・請負の契約書)

jp_stamp_duty
Read-onlyIdempotent

Look up Japanese stamp duty (印紙税) for a paper receipt for sales proceeds (領収書, 第17号の1 売上代金の受取書), a real-estate transfer contract (不動産売買契約書, 第1号の1) or a contract for work (請負契約書, 第2号), including the reduced rates for real-estate transfer and construction contracts made from 2014-04-01 to 2027-03-31. It looks up the amount in the NTA table for the document type the caller specifies (e.g. receipts under ¥50,000 are non-taxable); which document type a document is, is chosen by the caller (the user). amount is the tax-inclusive total written on the document (pass null when no amount is written; omitting it is an error); when consumption tax is stated separately (or both tax-inclusive and tax-exclusive prices are written), set consumption_tax_separately_stated with consumption_tax_amount, or pass amount_excluding_consumption_tax (with consumption_tax_separately_stated: true) instead of amount — consumption tax is then excluded, as the NTA circular says. Per NTA No.7108, a contract based on a construction contract that also lists design or other work is treated as a whole as a construction contract. Based on National Tax Agency tables (laws as of 2026-04-01). It does not decide which document number a document falls under, and does not cover other document types or electronic documents.

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": {
      "document_type": "<document_type>"
    },
    "name": "jp_stamp_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo書類の金額(円・消費税額等を含めた税込の合計)。消費税を区分して書いている時も税込の合計を入れる。金額を書いていないなら null を明示する(渡さないと誤り)。amount_excluding_consumption_tax とどちらか片方だけ
created_onNo書類を作った日(YYYY-MM-DD)。無ければ今日(日本の日付)
document_typeYes呼ぶ側(利用者)が選ぶ書類の種類。receipt=売上代金の領収書(第17号の1)、real_estate_transfer_contract=不動産の譲渡の契約書(第1号の1)、construction_contract=建設工事の請負(第2号。建設工事の契約に基づく書類なら、設計など建設工事以外の事を一緒に書いていても全体がこれ)、other_work_contract=建設工事以外の請負(第2号)
business_relatedNo領収書だけ。営業に関しない受取書なら false(非課税)。既定 true
consumption_tax_amountNo区分して書いた消費税額等(円)
amount_excluding_consumption_taxNo税抜の額(円)を amount の代わりに渡す時。消費税額等を区分して書いているか、税込と税抜の両方を書いている書類だけで、consumption_tax_separately_stated: true も要る。この額で表を引き、consumption_tax_amount は使わない
consumption_tax_separately_statedNo消費税額等を具体的に書いている時、または税込と税抜の両方を書いている時は true(消費税額=税込−税抜)。既定 false

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

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantive context: NTA table basis, law version as of 2026-04-01, the 2014-2027 reduced-rate window, non-taxable receipts under ¥50,000, and No.7108 treatment of mixed construction contracts. This is exactly the kind of domain behavior annotations cannot express.

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 and document-type list are front-loaded, but the body is one long, dense paragraph that repeats schema details and packs several conditional rules into em-dash clauses. It is informative but could be split or trimmed, especially the repeated document-type examples.

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-parameter tax lookup with a 100%-covered schema and an output schema, the description supplies the needed scope, exclusions, legal basis, and rate-period context. Nothing essential for correct invocation 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 100%, so baseline is 3; the description nonetheless adds cross-field logic in English—amount is tax-inclusive, null must be explicit, and either consumption_tax_amount with the flag or amount_excluding_consumption_tax replaces amount. It also explains why consumption tax is excluded. That is additional meaning beyond the schema, though much of it is duplicated in Japanese field descriptions.

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?

States a specific verb (look up) and resource (Japanese stamp duty) and enumerates the exact document types and form numbers it covers. An agent can tell this is a stamp-duty lookup, not a general tax or date tool, and knows the scope is paper documents only.

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?

Gives clear when-to-use conditions (paper receipt, real-estate transfer contract, contract for work) and when-not conditions (other document types, electronic documents; it does not classify the document). It does not name an alternative tool, but no sibling clearly overlaps, so routing guidance is effectively complete; 4 rather than 5 because it never says 'use X instead'.

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