Skip to main content
Glama

China Salary and Income Tax Calculator

Employer cost of a salary in China

employer_cost
Read-onlyIdempotent

What a salary in China costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity: shanghai = Shanghai; beijing = Beijing; shenzhen = Shenzhen; guangzhou = Guangzhou. Default shanghai.
elderlyNoSupporting parents aged 60+: none = No; only = Yes, only child (¥3,000/month); shared = Yes, shared with siblings (¥1,500/month). Default none.
childrenNoNumber of dependent children. Default 0.
educationNoContinuing education (¥400/month) Default false.
fx_per_eurNoExchange rate: 1 euro = this many CNY, for the euro amounts. Default 7.6 (indicative).
housing_dedNoHousing deduction: none = None; tier1 = Rent, tier-1 city (¥1,500/month); tier2 = Rent, large city (¥1,100/month); tier3 = Rent, other city (¥800/month); mortgage = First-home mortgage interest (¥1,000/month). Default none.
bonus_annualNoYearly bonus in CNY. Default 0.
gross_annualNoGross yearly salary in CNY
housing_fundNoHousing fund rate (%). Default 7.
budget_annualNoTotal yearly employer budget in CNY, to find the gross salary it allows
bonus_separateNoTax the year-end bonus separately. Uses the bonus amount field above. Separate taxation is usually cheaper at moderate incomes. Default true.
expat_allowancesNoTax-free expat allowances. Foreign nationals: housing, language training and children's school fees paid against receipts. (¥ / year). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds useful behavioural detail — employer contributions are itemised in the result and the tool runs in two directions — but says nothing about mutual exclusivity of gross_annual/budget_annual or required input when neither is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two dense sentences with no filler; the dual-direction behaviour is stated first and the selecting parameters last, which front-loads the most important information.

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?

For a 12-parameter calculator the description covers purpose and mode selection, and the schema carries the heavy per-parameter detail with no output schema to compensate for. It is slightly thin on which parameters only matter in one mode (e.g. budget_annual vs gross_annual) and on error behaviour when neither is supplied.

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 all twelve parameters, including the enums for city, elderly and housing_ded, are already documented in the schema. The description only restates the two amount parameters that drive the calculation, adding no syntax or format detail beyond structured data — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair: employer cost of a salary in China, with employer social contributions itemised, and explicitly covers the inverse direction (budget → gross). This clearly separates it from net_salary and gross_for_target_net, though it never names those 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?

"Give gross_annual or budget_annual" tells the agent exactly which parameter selects which computation mode, which is the key usage decision for this tool. It stops short of stating exclusions against siblings (e.g. when to prefer net_salary) or what happens if both/neither are supplied.

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