Skip to main content
Glama

China Salary Calculator

Net salary: China vs the Netherlands

compare_with_netherlands
Read-onlyIdempotent

Take-home pay of a job in China (with the situation options of net_salary) next to a job in the Netherlands (2026, optionally with the 8% holiday allowance and the 30% ruling), in euros, with the difference a year.

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": {
      "home_gross_annual": "<home_gross_annual>",
      "nl_gross_annual": "<nl_gross_annual>"
    },
    "name": "compare_with_netherlands"
  }
}

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.
housing_fundNoHousing fund rate (%). Default 7.
bonus_separateNoTax the year-end bonus separately. Uses the bonus amount field above. Separate taxation is usually cheaper at moderate incomes. Default true.
nl_gross_annualYesGross yearly salary in the Netherlands, in euros, without holiday allowance
expat_allowancesNoTax-free expat allowances. Foreign nationals: housing, language training and children's school fees paid against receipts. (¥ / year). Default 0.
home_gross_annualYesGross yearly salary in China, in CNY
nl_holiday_allowanceNoThe Dutch job pays 8% holiday allowance on top. Default true.
nl_thirty_percent_rulingNoThe 30% ruling applies in the Netherlands. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context the annotations cannot: results are normalized to euros, expressed per year, and the Dutch side assumes 2026 rules with optional 8% holiday allowance and 30% ruling. It does not explain how the CNY side is converted or what the returned comparison looks like.

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?

It is a single compact sentence with no wasted words, but the information is buried in stacked parentheticals and the key output detail ('in euros, with the difference a year') trails at the end rather than being front-loaded. Readable but awkwardly constructed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter tool with no output schema, the description should convey the shape of the result; it only says the comparison is in euros with an annual difference, leaving the structure of the returned figures unstated. Schema coverage is complete, so the parameter side is adequate, but the output side is thin.

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 coverage is 100%, so every one of the 14 parameters is already documented in the schema; the 3 baseline applies. The description adds only marginal orientation by noting that the China side uses the 'situation options of net_salary' and flagging the two Dutch toggles, without clarifying units or interactions beyond the schema.

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?

The description states a specific comparison resource: China take-home pay placed side by side with Netherlands take-home pay, expressed in euros as an annual difference. It is clearly distinct from the single-country sibling net_salary, though it references that tool rather than naming it as the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for comparing a Chinese offer against a Dutch offer, but there is no explicit when-to-use statement, no guidance on when to prefer net_salary for a single-country calculation, and no note on prerequisites such as needing both gross figures.

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