Skip to main content
Glama

France Salary and Income Tax Calculator

Employer cost of a salary in France

employer_cost
Read-onlyIdempotent

What a salary in France 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
cadreNoCadre (executive status) Default false.
impatNoImpatriate regime (recruited from abroad). Flat 30% of pay exempt from income tax for up to 8 years. Default false.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
isolatedNoRaising children alone (parent isolé). Unmarried with children living with you: one extra half-part. Default true.
mutuelleNoMutuelle, employee share (€ / month). Default 0.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final), 2024 (final). Default 2026. A year that is not listed is not available for this country.
bonus_annualNoYearly bonus in EUR. Default 0.
gross_annualNoGross yearly salary in EUR
budget_annualNoTotal yearly employer budget in EUR, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in EUR, 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), 2024 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025,
      +    2024
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that employer social contributions are itemised and that the tool computes in two directions, but with no output schema it does not describe the actual result shape, precision, or underlying assumptions.

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 sentences with no filler; the dual-mode purpose is stated first and the operative parameter hint last, so nothing is buried.

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 an 11-parameter, default-heavy, no-required-parameter calculator with no output schema, the description leaves real gaps: the behavior when neither gross_annual nor budget_annual is given, and what happens if both are supplied, are undefined. It also gives no sense of what the itemised breakdown contains, which matters without an output 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% with defaults documented for all 11 parameters, so the baseline is 3. The description earns an extra point by implying that gross_annual and budget_annual are mutually exclusive mode switches — a relationship the schema itself does not encode.

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?

It names a specific calculation and both directions: employer cost of a gross salary with itemised social contributions, and the inverse gross-from-budget. The framing ('costs the employer') implicitly separates it from net_salary and gross_for_target_net, though it never names a sibling to make the boundary explicit.

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 instruction 'Give gross_annual or budget_annual' does tell the agent how to select the mode, which is real usage guidance. It stops short of stating exclusions (what happens if both or neither are supplied) or when to prefer this over 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