Skip to main content
Glama

Romania Salary and Income Tax Calculator

Employer cost of a salary in Romania

employer_cost
Read-onlyIdempotent

What a salary in Romania 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.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
fx_per_eurNoExchange rate: 1 euro = this many RON, for the euro amounts. Default 4.97 (indicative).
bonus_annualNoYearly bonus in RON. Default 0.
gross_annualNoGross yearly salary in RON
budget_annualNoTotal yearly employer budget in RON, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in RON, for joint taxation and spouse allowances. Default 0.
kids_in_schoolNoChildren 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.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by promising itemised employer contributions in the result and flagging the inverse-budget mode, which matters since no output schema exists. Gaps remain on defaults behaviour and conflicting-input handling.

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 short sentences, front-loaded with the primary computation and immediately followed by the inverse mode and the required input. Nothing redundant.

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?

For a nine-parameter calculator with full schema documentation and strong annotations, the description covers purpose, jurisdiction, output character and mode selection. It would be complete with one clause on invalid or ambiguous input combinations, since no output schema exists to clarify results.

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 every parameter including age, spouse_income and kids_in_school is already documented, giving a baseline of 3. The description adds the mutual-alternative framing of gross_annual vs budget_annual, which the schema does not state, but says nothing about the optional demographic inputs.

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?

States a specific computation and both directions: employer cost of a Romanian salary with itemised social contributions, or the gross salary a budget allows. This implicitly separates it from net_salary and gross_for_target_net, but no sibling is named explicitly, so the differentiation is inferential 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 Guidelines4/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 drives which mode, which is clear context for use. It stops short of explicit when-to-use/when-not guidance against siblings like net_salary, and does not say what happens if both or neither are supplied.

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