Skip to main content
Glama

DinCat — learning and life in Japan

Japan take-home pay calculator (2026 rates)

calc_take_home_pay
Read-onlyIdempotent

Calculate a company employee's take-home pay in Japan from the 2026 official rates: health, nursing-care, child-support, pension and employment insurance, income tax and resident tax, per month and per year, for the first year in Japan and for later years. Calculated by program, not AI. Give either monthlySalary or annualSalary. Age and prefecture default to 30 and Tokyo when not given (marked in the result). The inputs are not stored.

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": "calc_take_home_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge (default 30). From 40 to 64, nursing-care insurance is added.
langNoLanguage of the reply and of the linked pages: ja = Japanese, zh = Simplified Chinese, en = English. Use the user's language.ja
industryNoEmployment insurance category: general (default), agriculture (agriculture, forestry, fisheries, sake brewing) or construction.
prefectureNoPrefecture where the user works (the health insurance rate depends on it), lowercase romaji, e.g. tokyo, osaka, kanagawa, aichi, fukuoka. Default tokyo.
annualBonusNoTotal bonuses per year in yen (default 0). With annualSalary it is the part of that total paid as bonuses.
annualSalaryNoYearly gross pay in yen including bonuses, excluding commuting allowance. Give this or monthlySalary.
bonusPaymentsNoHow many times a year the bonus is paid (default 2).
monthlySalaryNoMonthly base pay in yen before deductions (額面), excluding commuting allowance. Give this or annualSalary.
monthlyCommuteNoMonthly commuting allowance in yen (default 0): not taxed, but counted for social insurance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond them: 'Calculated by program, not AI' and 'The inputs are not stored' (a privacy guarantee). It stops short of describing return shape or any rate-limit or accuracy caveats, so it is a modest add over the annotations rather than a rich one.

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?

Three dense sentences, front-loaded with the calculation scope, then input rules, then the privacy and provenance notes. Nearly every clause carries weight; the 'first year in Japan and later years' phrase is slightly compressed but still informative.

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?

With no output schema, the description carries the burden of return shape and does so adequately: 'per month and per year' plus defaults 'marked in the result' tell the agent what comes back. For a nine-parameter financial calculator it is complete enough to invoke correctly, though it does not describe the breakdown fields returned.

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 every one of the nine parameters is already documented, including the nursing-care age rule and prefecture-driven health insurance rate. The description only restates the monthly-vs-annual choice and the default values, adding emphasis rather than new meaning; baseline 3 is appropriate.

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 and resource ('Calculate a company employee's take-home pay in Japan'), pins the rate year, enumerates the deductions covered, and scopes the output to monthly and yearly figures. An agent can distinguish it from get_visa_rules or search_library without opening the schema.

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 concrete invocation guidance: 'Give either monthlySalary or annualSalary', and states that age and prefecture fall back to 30 and Tokyo and are marked in the result. No explicit when-not-to-use, but the sibling set (visa rules, library) is unrelated, so no routing conflict needs resolving.

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