french-admin-mcp

simuler_chomage

Estimate French unemployment benefits (ARE) by entering your average monthly salary, months worked, age, and contract termination reason. Get daily/monthly amount, duration, and France Travail steps.

Instructions

Estime l'allocation chômage (ARE — Aide au Retour à l'Emploi). Calcule le montant journalier/mensuel, la durée d'indemnisation et les démarches France Travail. Barème 2026.

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": {
      "salaireBrutMensuelMoyen": "<salaireBrutMensuelMoyen>",
      "moisTravailles": "<moisTravailles>",
      "age": "<age>",
      "motifRupture": "<motifRupture>"
    },
    "name": "simuler_chomage"
  }
}

Input Schema

Name	Required	Description
`salaireBrutMensuelMoyen`	Yes	Salaire brut mensuel moyen des 24 derniers mois
`moisTravailles`	Yes	Nombre de mois travaillés sur les 24 derniers mois (minimum 6 pour être éligible)
`age`	Yes	Âge au moment de la fin de contrat
`motifRupture`	Yes	Motif de la rupture du contrat

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Jun 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It mentions 'Estime' implying a simulation, but does not explicitly state if it is read-only or safe. It adds no details on preconditions or side effects.

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 a single concise sentence that front-loads the main purpose and includes key details (2026 rates, ARE). Every word earns its place.

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?

Given four required parameters and no output schema, the description covers what the tool does (estimates and calculates) and offers reasonable completeness. Missing output format details but adequate for a simulation tool.

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 parameters are already documented. The tool description adds context on what is calculated (e.g., daily/monthly amount) but does not add meaning beyond what the schema provides for individual parameters.

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 explicitly states the tool estimates unemployment benefits (ARE), calculates daily/monthly amounts, duration, and steps, distinguishing it from sibling tools like verifier_droits_chomage_demission which verifies rights for specific cases.

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 description provides context (estimating ARE with 2026 rates) but lacks explicit guidance on when to use this tool vs alternatives (e.g., checking eligibility or verifying specific rights). No exclusions or when-not-to-use are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.