Poland Salary Calculator

Net salary: Poland vs the Netherlands

compare_with_netherlands

Read-onlyIdempotent

Take-home pay of a job in Poland (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

Name	Required	Description
`age`	No	Age; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
`ppk`	No	Employee Capital Plan (PPK). You pay 2%, the employer 1.5% (taxable for you). Default false.
`joint`	No	Joint return with spouse Default true.
`author`	No	Share of pay under copyright. Creative work (software, design, writing): 50% costs on that part, up to 120,000 zł of costs. (%). Default 0.
`married`	No	Married or registered partner. Default false.
`children`	No	Number of dependent children. Default 0.
`commuter`	No	Live outside the town where you work. Standard costs of 300 zł instead of 250 zł a month. Default false.
`fx_per_eur`	No	Exchange rate: 1 euro = this many PLN, for the euro amounts. Default 4.25 (indicative).
`bonus_annual`	No	Yearly bonus in PLN. Default 0.
`return_relief`	No	Return relief (ulga na powrót). For 4 years after moving to Poland, for Polish citizens or people with Polish roots who lived abroad for 3+ years. Default false.
`spouse_income`	No	Partner's gross yearly income in PLN, for joint taxation and spouse allowances. Default 0.
`nl_gross_annual`	Yes	Gross yearly salary in the Netherlands, in euros, without holiday allowance
`home_gross_annual`	Yes	Gross yearly salary in Poland, in PLN
`nl_holiday_allowance`	No	The Dutch job pays 8% holiday allowance on top. Default true.
`nl_thirty_percent_ruling`	No	The 30% ruling applies in the Netherlands. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered. The description adds the useful facts that the model is 2026 and that results are expressed in euros with an annual delta, but with no output schema it says little about the return structure beyond that one phrase.

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?

A single sentence with no filler, front-loading the compared entities and ending on the result. It loses a point for an over-stuffed parenthetical and awkward phrasing ('next to a job', 'with the difference a year') that slows parsing.

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 15-parameter comparison tool with no output schema, the description gives the headline result and units but does not explain how the two salary figures are combined, what currency the difference is reported in, or how the fx rate interacts with the euro/PLN split. Adequate to select the tool, thin for anticipating output.

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 all 15 parameters, including fx_per_eur, holiday allowance and the 30% ruling, are already documented in the schema. The description only reiterates a couple of the toggles and adds no format, unit, or interaction detail beyond them, so the baseline 3 applies.

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 names the specific resource (take-home pay in Poland vs the Netherlands) and the output shape (euros plus annual difference), and it points at the sibling net_salary for the Poland-side options. It is distinguishable from net_salary and employer_cost, though the sentence is dense and slightly garbled ('with the difference a year').

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?

By saying the Poland side uses 'the situation options of net_salary' it implies this is the two-country variant of that tool, but it never states when to pick this over calling net_salary alone or over gross_for_target_net. Usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Poland 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?