Skip to main content
Glama

french-rental-compliance

by com.adminlanding
OverviewDiscussionsAdmin

Frontalier health cover — LAMal vs CMU

compare_lamal_cmu
Read-only

Frontalier health cover: LAMal (CH) vs CMU/PUMa (FR). · Couverture santé frontalier : LAMal (CH) ou CMU (FR). — Estimates the monthly cost of the two health-insurance options a France–Switzerland cross-border worker chooses between (droit d'option): Swiss LAMal (in CHF) vs the French contribution (in EUR, 8 % of the worker's OWN income of year N-2 above 25 % of the PASS — CSS art. L. 380-3-1 IV and D. 380-2). Give income_n2_eur (own net income as declared); without it the French figure is an UPPER estimate from the gross salary, flagged as such. Dependants are priced by age band (0-18 child, 19-25 young adult, 26+ adult). Deterministic official premium/rate tables — no AI. Returns both monthly figures, the rules of the option (window, reception by the Swiss authority, default, who has it) and how to transmit the form. Recommends neither system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageYesWorker's age.
cantonYesSwiss canton of work — two-letter code, any of the 26 cantons.
salary_chfNoAnnual gross Swiss salary in CHF — used only when income_n2_eur is missing, and then the French figure is an upper estimate.
children_agesNoAges of dependants (optional) — priced by band (≤18 / 19-25 / 26+).
income_n2_eurNoThe worker's OWN income of year N-2 in EUR, net, as declared (salaries + other own income; half of income held in common) — the base of the French contribution (CSS D. 380-2). Not the household revenu fiscal de référence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / canton / description
      Previous value: -"Swiss border canton (GE, VD, JU, NE, BS, VS)."New value: +"Swiss canton of work — two-letter code, any of the 26 cantons."
    • changedInput schema / properties / canton / enum
      Previous value: -[
-  "GE",
-  "VD",
-  "JU",
-  "NE",
-  "BS",
-  "VS"
-]New value: +[
+  "AG",
+  "AI",
+  "AR",
+  "BE",
+  "BL",
+  "BS",
+  "FR",
+  "GE",
+  "GL",
+  "GR",
+  "JU",
+  "LU",
+  "NE",
+  "NW",
+  "OW",
+  "SG",
+  "SH",
+  "SO",
+  "SZ",
+  "TG",
+  "TI",
+  "UR",
+  "VD",
+  "VS",
+  "ZG",
+  "ZH"
+]
    • addedInput schema / properties / income_n2_eur
      Added value: +{
+  "description": "The worker's OWN income of year N-2 in EUR, net, as declared (salaries + other own income; half of income held in common) — the base of the French contribution (CSS D. 380-2). Not the household revenu fiscal de référence.",
+  "maximum": 5000000,
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / salary_chf / description
      Previous value: -"Annual Swiss salary in CHF."New value: +"Annual gross Swiss salary in CHF — used only when income_n2_eur is missing, and then the French figure is an upper estimate."
    • changedInput schema / required
      Previous value: -[
-  "salary_chf",
-  "age",
-  "canton"
-]New value: +[
+  "age",
+  "canton"
+]
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint, but the description adds rich behavior: values come from deterministic official premium/rate tables (no AI), it recommends neither system, and it returns option rules (window, reception by Swiss authority, default, who holds it) plus form-transmission guidance. This goes far beyond the annotation coverage.

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?

Dense but front-loaded and every sentence carries meaning; the method, fallback, and legal basis are stated efficiently. The duplicated bilingual header line ('Couverture santé frontalier...') is mildly redundant for an agent but does not dilute the core content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by describing the returns (both monthly figures, option rules, transmission steps). All five parameters are documented at full coverage, so an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds real meaning beyond the schema: income_n2_eur is the worker's OWN net N-2 income, explicitly 'not the household revenu fiscal de référence', and dependants are priced by age band. salary_chf's fallback role is also clarified.

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 specific verb (estimates monthly cost) and a precise resource (the two frontalier health-insurance options, LAMal vs CMU/PUMa), and frames it as the droit d'option choice. An agent can distinguish this from sibling calculators like compare_family_allowances purely from the text.

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?

Explains the conditional use of parameters: give income_n2_eur for the exact French figure, otherwise salary_chf yields an upper estimate explicitly flagged as such. This covers when and how to invoke it well, but names no alternative sibling tools or exclusion conditions.

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

All french-rental-compliance toolsInspect
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