Skip to main content
Glama

JobCrawls

Calculate net salary in Finland (gross to net, employer cost)

calculate_net_salary_finland
Read-onlyIdempotent

Gross-to-net salary calculator for Finland, from the JobCrawls tax iceberg calculator. Use for questions like "what is 4000 gross net in Finland", "paljonko jää käteen 4200 euron bruttopalkasta Helsingissä", or "vad blir nettolönen på 3800 brutto i Helsingfors". Give a gross salary (EUR per month by default, or per year), or a target net to get the gross it takes, and optionally the municipality, employer size, age, dependent children, commuting costs and investment income. It does not accept church membership or union fees. The linked page comes back in the language detected from "municipality" when locale is omitted, else English; pass locale explicitly to override. Returns monthly and annual breakdowns: employee pension and unemployment contributions, state, municipal, church and Yle taxes, net pay, employer contributions and the true cost of employment, plus the effective tax rate, the assumptions used and a link to the same scenario on jobcrawls.com. Uses the current tax year's official Finnish parameters; an estimate, not tax advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoAge in years, affects pension and unemployment contributions.
netNoTarget net pay in euros (same period): the tool solves the gross salary that leaves this in hand. Give either gross or net.
grossNoGross salary in euros, per month unless period is "year". Give either gross or net.
localeNoSet this to the language of the user's message (fi for Finnish, sv for Swedish, en for English or any other language), even when the job titles or place names in it are English. Language of the result notes, the inline card and the linked page. When omitted, detected from "municipality" if it is given in Finnish or Swedish form; otherwise defaults to en.
periodNoPeriod of every money amount given. Default month.
dividendsNoListed-company dividends in the same period (capital income).
includeVatNoAlso subtract the VAT paid when the net is spent (an estimate). Default false.
capitalGainsNoCapital gains net of acquisition cost in the same period.
employerSizeNoEmployer payroll size for the unemployment-insurance rate (large = payroll above about EUR 2.5 million). Omit for a blended average.
municipalityNoFinnish municipality name, e.g. "Helsinki" or "Espoo". Omit for the national-average municipal tax rate.
commutingCostsNoCommuting costs in the same period; deductible above the own-liability share, capped.
isSoleGuardianNoSingle parent with dependent children (child deduction).
dependentChildrenNoNumber of dependent children, affects the child tax deduction.
unlistedDividendsNoDividends from the person's own unlisted company in the same period (8% yield rule).
unlistedNetAssetsNoMathematical value of the person's shares in that company, EUR (a stock, not per period).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe inputs the calculation used, after defaults.
ratesYes
annualYesBreakdown per year, EUR.
localeYes
methodYes
monthlyYesBreakdown per month, EUR.
pageUrlYesThe same scenario on jobcrawls.com, where church tax and union fees can be set privately.
taxYearYes
currencyYes
assumptionsYes
investmentsYesCapital income breakdown, or null when no investment income was given.
destinationsYesWhere the taxes and contributions go, EUR per year.
icebergSvgUrlYesImage illustrating the breakdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish the read-only idempotent safety profile, and the description adds substantial context beyond them: locale detection rules, the returned breakdown fields, the current-tax-year basis, and an explicit 'estimate, not tax advice' caveat.

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 dense paragraph, but front-loaded with purpose and examples, and nearly every sentence carries distinct information (inputs, exclusions, locale, returns, caveat). Slightly heavy, yet nothing is padding.

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

Completeness5/5

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

For a 15-parameter zero-required calculator with an output schema, the description covers inputs, edge cases (locale/municipality interplay), output shape, and limitations. Since an output schema exists, the return-value prose is bonus rather than a gap.

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 description adds cross-parameter meaning the schema cannot: the gross-vs-net mutual-exclusion intent, the period default, and the interaction where municipality's language form drives locale detection. It adds real value on top of a fully documented 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?

States a specific verb and resource ('Gross-to-net salary calculator for Finland') plus the domain context (JobCrawls tax iceberg calculator). It is trivially distinguishable from the job-search siblings, which share no overlap.

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

Usage Guidelines5/5

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

Gives concrete example questions in three languages, explains the gross-or-net input modes, enumerates the optional dimensions, and states explicit exclusions ('does not accept church membership or union fees'). An agent knows exactly when and how to call it.

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