Skip to main content
Glama

Morocco Salary and Income Tax Calculator

Employer cost of a salary in Morocco

employer_cost
Read-onlyIdempotent

What a salary in Morocco 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
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.
fx_per_eurNoExchange rate: 1 euro = this many MAD, for the euro amounts. Default 10.7 (indicative).
pension_pctNoVoluntary employee pension contribution through payroll, % of salary. Default 0.
bonus_annualNoYearly bonus in MAD. Default 0.
gross_annualNoGross yearly salary in MAD
budget_annualNoTotal yearly employer budget in MAD, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in MAD, for joint taxation and spouse allowances. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds that employer social contributions are itemised and that the operation can be reversed, which is useful context, but it does not describe the return format or calculation assumptions beyond what the schema and annotations imply.

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?

The description is two sentences, front-loaded with the core purpose, and wastes no words. The second sentence directly tells the caller which key parameters drive the two modes.

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 read-only calculation tool with full schema coverage and clear annotations, the description provides enough context to call it correctly: it explains both directions and the key parameter choice. It could be more complete by noting what the itemised output contains or how tax_year and household parameters affect the result, but those details are largely covered by the schema.

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 schema documents all nine parameters fully. The description adds meaningful semantics by stating that the user should supply either gross_annual or budget_annual, clarifying the mutually exclusive calculation modes beyond the schema's flat parameter list.

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 clearly states the tool's purpose: calculating employer cost from a gross salary with itemised social contributions, or inversely finding the gross salary allowed by a total budget. It is specific about the country (Morocco) and direction, but does not explicitly name or distinguish sibling tools such as gross_for_target_net or net_salary.

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 closing sentence 'Give gross_annual or budget_annual' provides clear guidance on which parameter to supply for each calculation mode, but the description does not explain when to use this tool versus alternatives like net_salary or gross_for_target_net.

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