Skip to main content
Glama

french-rental-compliance

by com.adminlanding

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 French CMU/PUMa (in EUR, a % of income). 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 data year, plus how to transmit the signed choice form (the CPAM's dedicated online téléservice).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageYesWorker's age.
cantonYesSwiss border canton (GE, VD, JU, NE, BS, VS).
salary_chfYesAnnual Swiss salary in CHF.
children_agesNoAges of dependants (optional) — priced by band (≤18 / 19-25 / 26+).

TDQS

A4.5/5.0
Behavior5/5

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

Adds meaningful behavior beyond annotations: deterministic official rate tables with no AI, dependants priced by age bands, and returns both monthly figures, the data year, and transmission instructions. Aligns with readOnlyHint=true and openWorldHint=false without contradiction.

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?

Core content is dense and useful, but the opening bilingual phrase duplicates the title before the explanatory sentence begins. Slightly verbose; the first clause could be removed without losing information.

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?

No output schema exists, yet the description compensates by specifying the exact returns: both monthly figures, the data year, and how to transmit the signed choice form. All key inputs, pricing logic, and currencies are covered, providing a complete picture for an agent.

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 covers 100% of parameters, so baseline is 3. The description adds value by clarifying that CMU/PUMa is a percentage of income, that dependants are grouped into specific age bands, and that the salary context is annual Swiss CHF.

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 the exact verb 'Estimates' and resource: monthly cost of the two health-insurance options for a France–Switzerland cross-border worker. Explicitly names LAMal vs CMU/PUMa, making it instantly distinguishable from sibling tools like compare_family_allowances.

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?

Clearly identifies when to use: when a France–Switzerland cross-border worker is choosing between LAMal and CMU/PUMa under the droit d'option. Does not explicitly name sibling alternatives or exclusion conditions, but the context is unambiguous enough for 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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool is tied to a specific legal or payroll calculation, and the names clearly indicate their target: salary, rent revision, tenant notice, DPE restrictions, quasi-resident status, zone-tendue lookup, family allowances, and health insurance. Some overlap exists because rent revision and DPE checks both involve F/G rent freezes, and tenant notice relies on zone-tendue data, but descriptions keep boundaries clear.

Naming Consistency5/5

All tool names follow the same snake_case verb_noun pattern with a concise legal/domain object. The verbs vary by nature of action—calculate_, check_, compare_—but each is consistent and semantically meaningful.

Tool Count5/5

Eight tools is a well-scoped number for a specialist compliance server. Each tool handles a distinct calculation or legal lookup, and none feels redundant or purely decorative.

Completeness4/5

The set covers the main rental-revision, tenant-notice, DPE-restriction, zone-tendue, and cross-border worker salary/benefit comparisons well. Minor gaps remain around related compliance details such as rental deposits, landlord-side termination, or deeper Swiss tax filing checks, but they are not fatal to the tool set’s stated purpose.

Resources