Morocco Salary Calculator

Net salary: Morocco vs the Netherlands

compare_with_netherlands

Read-onlyIdempotent

Take-home pay of a job in Morocco (with the situation options of net_salary) next to a job in the Netherlands (2026, optionally with the 8% holiday allowance and the 30% ruling), in euros, with the difference a year.

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": {
      "home_gross_annual": "<home_gross_annual>",
      "nl_gross_annual": "<nl_gross_annual>"
    },
    "name": "compare_with_netherlands"
  }
}

Input Schema

Name	Required	Description
`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 MAD, for the euro amounts. Default 10.7 (indicative).
`pension_pct`	No	Voluntary employee pension contribution through payroll, % of salary. Default 0.
`bonus_annual`	No	Yearly bonus in MAD. Default 0.
`spouse_income`	No	Partner's gross yearly income in MAD, for joint taxation and spouse allowances. Default 0.
`nl_gross_annual`	Yes	Gross yearly salary in the Netherlands, in euros, without holiday allowance
`home_gross_annual`	Yes	Gross yearly salary in Morocco, in MAD
`nl_holiday_allowance`	No	The Dutch job pays 8% holiday allowance on top. Default true.
`nl_thirty_percent_ruling`	No	The 30% ruling applies in the Netherlands. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/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 context beyond that: the 2026 tax year, normalization of both sides into euros, and the fact that a yearly difference is produced. It does not say how the FX rate affects the comparison or what a missing/invalid rate does, which would be the next useful detail.

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?

One dense sentence that front-loads the comparison and its output framing, with no filler. The telegraphic phrasing ('with the difference a year', 'next to a job') is slightly awkward but does not obscure meaning.

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 ten-parameter comparison tool with no output schema, the description covers the essentials: what is compared, the tax year, the currency of the result, and that a difference is returned. It could say more about the shape of the returned comparison (per-country breakdown vs single delta), but nothing critical to invoking it is missing.

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 one of the ten parameters is already documented with defaults and units. The description only echoes the holiday allowance and 30% ruling flags that the schema already explains, adding no new semantics such as how fx_per_eur interacts with the Moroccan bonus or spouse income.

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 concrete computation: Morocco take-home pay set against Netherlands take-home pay, expressed in euros with the annual difference. It also names the tax year (2026) and the two optional Dutch schemes, and explicitly points to net_salary for the underlying situation options, so the agent can separate it from that sibling without opening a schema.

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?

The reference to 'the situation options of net_salary' implies this tool is the two-country variant, which is a usable hint about when to pick it over net_salary. However, it never states when not to use it, nor does it distinguish it from gross_for_target_net or employer_cost, 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 Morocco 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?