China Salary Calculator

Gross salary needed for a net amount in China

gross_for_target_net

Read-onlyIdempotent

The gross yearly salary in China that leaves a given take-home pay, with the same situation options as net_salary. Use it to set a salary ask or check an offer.

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": {
      "net_target": "<net_target>"
    },
    "name": "gross_for_target_net"
  }
}

Input Schema

Name	Required	Description
`city`	No	City: shanghai = Shanghai; beijing = Beijing; shenzhen = Shenzhen; guangzhou = Guangzhou. Default shanghai.
`period`	No	Whether net_target is per year or per month. Default year.
`elderly`	No	Supporting parents aged 60+: none = No; only = Yes, only child (¥3,000/month); shared = Yes, shared with siblings (¥1,500/month). Default none.
`children`	No	Number of dependent children. Default 0.
`education`	No	Continuing education (¥400/month) Default false.
`fx_per_eur`	No	Exchange rate: 1 euro = this many CNY, for the euro amounts. Default 7.6 (indicative).
`net_target`	Yes	Take-home pay wanted, in CNY
`housing_ded`	No	Housing 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_annual`	No	Yearly bonus in CNY. Default 0.
`housing_fund`	No	Housing fund rate (%). Default 7.
`bonus_separate`	No	Tax the year-end bonus separately. Uses the bonus amount field above. Separate taxation is usually cheaper at moderate incomes. Default true.
`expat_allowances`	No	Tax-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.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world calculation. The description adds that the result is a gross yearly salary in China and that it shares situation options with net_salary, but it does not disclose calculation assumptions, tax-year scope, or precision beyond what the schema implies.

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?

The description is two short sentences with no wasted wording. The core purpose is front-loaded, followed by a compact usage note.

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 tax calculation tool with no output schema, the description is brief but the schema fully documents every parameter and the annotations cover safety behavior. It could say more about the return value or calculation assumptions, but it is largely complete for an agent to select and invoke the tool.

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 12 parameters are already documented in the input schema. The description adds only the high-level note that the situation options match net_salary, without adding parameter-level meaning beyond the schema.

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 states a specific inverse calculation: the gross yearly salary in China that produces a given take-home pay. It also links the tool to net_salary by saying it uses the same situation options, which helps distinguish it from the sibling that likely computes net pay from gross.

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 gives clear use cases: setting a salary ask or checking an offer. It does not explicitly state when not to use it or name alternatives beyond the implicit relationship to net_salary, so it falls 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.

All China Salary Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?