Romania Salary Calculator

Net salary in Romania (2026)

net_salary

Read-onlyIdempotent

Take-home pay for an employee in Romania from a gross yearly salary in RON, with 2026 rules: every tax and contribution itemised with its local name, the effective and marginal rate, employer cost and the step-by-step workings. Covers: 10% flat tax after CAS and CASS; Personal deduction by dependants for low wages, extra for under-26s; Extra deduction for children in education; Employer work insurance contribution.

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": {
      "gross_annual": "<gross_annual>"
    },
    "name": "net_salary"
  }
}

Input Schema

Name	Required	Description
`age`	No	Age; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
`married`	No	Married or registered partner. Default false.
`children`	No	Number of dependent children. Default 0.
`fx_per_eur`	No	Exchange rate: 1 euro = this many RON, for the euro amounts. Default 4.97 (indicative).
`bonus_annual`	No	Yearly bonus in RON. Default 0.
`gross_annual`	Yes	Gross yearly salary in RON, without bonus
`spouse_income`	No	Partner's gross yearly income in RON, for joint taxation and spouse allowances. Default 0.
`kids_in_school`	No	Children are in education. Extra deduction of 100 RON a month per child enrolled in school. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the output shape: itemised tax and contribution lines with local names, effective and marginal rates, employer cost, and step-by-step workings.

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?

The core purpose is front-loaded in the first clause, followed by a compact 'Covers:' list of the rule set. It is dense but every clause carries domain information; the only mild redundancy is repeating deduction rules that the schema already documents.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by enumerating the itemised tax lines, effective/marginal rates, employer cost and workings. For an 8-parameter but single-required-parameter calculation tool, this is close to complete, missing only a note on units/rounding of the returned figures.

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 every parameter is already documented, including the age, children and kids_in_school effects. The description's mentions of personal deduction by dependants, under-26 reliefs and the child education deduction largely restate what the schema already says, so it adds only marginal meaning 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 states a specific verb and resource: take-home pay for a Romanian employee computed from a gross yearly salary in RON under 2026 rules. It is clearly distinguishable from siblings like employer_cost or tax_rules_covered, though it never explicitly names the inverse tool gross_for_target_net, so the differentiation is implicit rather than stated.

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 implied by the phrasing 'from a gross yearly salary', which tells the agent this is the gross-to-net direction. However, there is no explicit when-to-use/when-not guidance and no mention of the sibling gross_for_target_net, which handles the opposite direction, leaving the agent to infer the routing.

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

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