Romania Salary Calculator

Gross salary needed for a net amount in Romania

gross_for_target_net

Read-onlyIdempotent

The gross yearly salary in Romania that leaves a given take-home pay, with the same situation options as net_salary. Use it to set a salary ask or check an offer.

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": {
      "net_target": "<net_target>"
    },
    "name": "gross_for_target_net"
  }
}

Input Schema

Name	Required	Description
`age`	No	Age; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
`period`	No	Whether net_target is per year or per month. Default year.
`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).
`net_target`	Yes	Take-home pay wanted, in RON
`bonus_annual`	No	Yearly bonus in RON. Default 0.
`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.9/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive calculation. The description adds that the result is a gross yearly salary and that it shares situation options with net_salary, but it does not explain calculation assumptions, rounding, or how the period parameter affects the returned gross figure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded and no wasted wording. The usage sentence is brief and adds practical context.

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 nine-parameter calculator with no output schema, the description should clarify the returned currency, rounding, and whether the result follows the period parameter. It says 'gross yearly salary' while the schema allows a monthly net target, leaving an ambiguity about the output period.

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 all nine parameters are already documented in the schema. The description only adds that the situation options mirror net_salary, which is marginally useful but does not add parameter-level meaning beyond the 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?

The description states a specific inverse calculation: the gross Romanian salary that yields a given net take-home pay. It clearly distinguishes the tool from the forward-looking net_salary sibling by naming the relationship between gross and net.

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

Usage Guidelines4/5

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

It gives clear usage contexts: setting a salary ask or checking an offer. It does not explicitly state when to use net_salary instead, though the inverse relationship is implied by the purpose.

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?