Skip to main content
Glama

french-rental-compliance

by com.adminlanding
OverviewDiscussionsAdmin

Family allowances — Swiss vs French (frontalier)

compare_family_allowances
Read-only

Family allowances: Swiss vs French for a frontalier. · Allocations familiales : Suisse ou France pour un frontalier. — Compares the family allowances a cross-border worker's household is due under the Swiss canton's rules (BSV 2026 table, LAFam art. 3 age limits; paid monthly with the salary) vs the French CAF (F13213 amounts, modulated by the household's N-2 resources band), and the EU 883/2004 art. 68 differential when the other parent has an activity or an assimilated situation in France. Deterministic official tables — no AI. Returns Swiss monthly + annual (CHF), CAF monthly (EUR), the differential, per-child detail, the notes and the data year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cantonYesSwiss canton of work — two-letter code, any of the 26 cantons.
childrenYesThe children (at least one).
caf_income_bandNoThe household's CAF resources band (revenu net catégoriel of year N-2; service-public F13213): full rate, half or quarter. Omitted → full rate, and the result says so.
spouse_works_in_franceNoDoes the OTHER parent have an activity in France (employed or self-employed) or an assimilated situation there (French unemployment, sickness or maternity benefits, paid leave, parental leave treated as activity — Decision F1)? Yes → the CAF pays first and Switzerland pays the difference (Reg. 883/2004 art. 68).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / caf_income_band
      Added value: +{
+  "description": "The household's CAF resources band (revenu net catégoriel of year N-2; service-public F13213): full rate, half or quarter. Omitted → full rate, and the result says so.",
+  "enum": [
+    "full",
+    "half",
+    "quarter"
+  ],
+  "type": "string"
+}
    • 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"
+]
    • changedInput schema / properties / children / items / properties / age / description
      Previous value: -"Child's age."New value: +"Child's completed age."
    • changedInput schema / properties / children / items / properties / in_training / description
      Previous value: -"In education/training (extends eligibility)."New value: +"In post-compulsory training (training allowance from 15 at the earliest, until 25 at the latest — LAFam art. 3), or still at school after 16."
    • addedInput schema / properties / children / items / properties / incapable
      Added value: +{
+  "description": "Unable to exercise a gainful activity (art. 7 LPGA): child allowance until 20.",
+  "type": "boolean"
+}
    • changedInput schema / properties / spouse_works_in_france / description
      Previous value: -"Does the spouse work in France? (triggers the EU differential)."New value: +"Does the OTHER parent have an activity in France (employed or self-employed) or an assimilated situation there (French unemployment, sickness or maternity benefits, paid leave, parental leave treated as activity — Decision F1)? Yes → the CAF pays first and Switzerland pays the difference (Reg. 883/2004 art. 68)."
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / children / items / additionalProperties
      Removed value: -false
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: deterministic official tables with no AI, named sources (BSV 2026, LAFam art. 3, service-public F13213, Reg. 883/2004 art. 68), and the data year. It does not cover edge cases like unsupported canton/child combinations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core comparison sentence is front-loaded and dense with useful specifics, but the leading bilingual title/duplicate ('Family allowances: Swiss vs French... · Allocations familiales : Suisse ou France...') repeats the same information in two languages without adding meaning, and the single long sentence packs legal citations that a selecting agent does not need.

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?

With no output schema, the description correctly takes on the return shape: Swiss monthly + annual in CHF, CAF monthly in EUR, the differential, per-child detail, notes and data year. Combined with the source citations and determinism claim, this is nearly sufficient for a moderately complex calculator; only unsupported-case behavior is unstated.

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%, with enums and per-field descriptions for canton, children, caf_income_band and spouse_works_in_france, so the baseline is 3. The description adds the legal rationale behind the differential (CAF pays first, Switzerland pays the difference) but largely restates semantics already present in the schema.

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 precise verb ('compares') and a scoped resource: family allowances for a cross-border worker under Swiss canton rules vs French CAF, plus the EU 883/2004 art. 68 differential. This is clearly distinguishable from siblings such as compare_lamal_cmu or calculate_teletravail_frontalier.

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 implies the use case (a frontalier household with children and possibly a spouse active in France) but never states when to use this tool versus alternatives, nor does it name any sibling. The conditions for the differential are described, but only as domain logic, not as guidance on tool selection.

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