Skip to main content
Glama

Poland Salary and Income Tax Calculator

Employer cost of a salary in Poland

employer_cost
Read-onlyIdempotent

What a salary in Poland 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
ageNoAge; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
ppkNoEmployee Capital Plan (PPK). You pay 2%, the employer 1.5% (taxable for you). Default false.
jointNoJoint return with spouse Default true.
authorNoShare of pay under copyright. Creative work (software, design, writing): 50% costs on that part, up to 120,000 zł of costs. (%). Default 0.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
commuterNoLive outside the town where you work. Standard costs of 300 zł instead of 250 zł a month. Default false.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.
fx_per_eurNoExchange rate: 1 euro = this many PLN, for the euro amounts. Default 4.25 (indicative).
bonus_annualNoYearly bonus in PLN. Default 0.
gross_annualNoGross yearly salary in PLN
budget_annualNoTotal yearly employer budget in PLN, to find the gross salary it allows
return_reliefNoReturn 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_incomeNoPartner's gross yearly income in PLN, for joint taxation and spouse allowances. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds that the forward result itemises employer social contributions. It does not say what happens if both gross_annual and budget_annual are supplied (precedence, error, or mutual exclusion), nor whether non-financial params like age or children change the employer-cost result.

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?

Two short sentences, front-loaded with the primary computation before the reverse case, with no filler. The phrasing is slightly telegraphic (e.g. "(employer social contributions itemised)" is compressed into a parenthetical), but nothing is wasted.

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, no-output-schema tool the description covers the core mechanic, but it never explains that most of the personal-tax parameters (age, married, children, joint, return_relief) exist for the underlying tax model and may not alter the employer-cost direction. An agent has no cue about which of the 14 inputs actually matter in each mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the sentence about supplying one of gross_annual or budget_annual adds mode-selection meaning the schema does not encode — both are listed there as plain optional numbers with no stated exclusivity. That is real information beyond the structured fields.

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 a specific computation (employer cost of a salary in Poland) and, unusually, its inverse (gross salary a budget affords), which cleanly separates it from net_salary and gross_for_target_net. It stops short of explicitly naming those siblings, so an agent must infer the boundary itself.

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?

"Give gross_annual or budget_annual" tells the agent which input selects which direction, which is genuine selection guidance for the two modes. There is no guidance on when to prefer this tool over the sibling calculators (e.g. net salary vs employer cost vs gross-for-target-net), so the alternatives remain implicit.

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