french-rental-compliance

Security-deposit restitution calculator — due date, late penalty, vétusté apportionment

calculate_deposit_restitution

Read-only

Deposit restitution: due date, 10 %/month late penalty, vétusté-apportioned retentions. · Restitution du dépôt de garantie : date limite, majoration de 10 % par mois de retard, retenues avec vétusté. — For a French residential lease (loi n° 89-462 art. 22 / art. 25-6): the restitution deadline (1 month from the remise des clés when the exit état des lieux matches the entry one, 2 months otherwise), the late penalty (10 % of the monthly rent en principal per monthly period started late; not due when the delay results from the tenant not having given the address of the new home), the provision a landlord may keep in an immeuble collectif (duly justified, at most 20 % of the deposit — art. 22, al. 5: a ceiling, the amount is the landlord's), the legal deposit cap (1 month unfurnished / 2 months furnished, when lease_type is given) and, for each damage line, the share chargeable to the tenant after vétusté (usure normale) — under the grille of the lease when given, otherwise an ILLUSTRATIVE grille (no official grille exists — décret n° 2016-382 art. 4 defers to accords collectifs; the response says so). Nothing is assumed: the age of an element a grille applies to is asked for, the lease type and the provision amount are left out when not given. Same figures whichever party asks: pass perspective 'landlord' (justify a retention) or 'tenant' (contest one) — only next_steps change. Ask the user for amounts and dates in plain words; damage items as 'what, repair cost, age of the element'. Deterministic rules, not AI. General information, not legal advice.

Input Schema

TableJSON Schema

Name	Required	Description
`damages`	No	Damage lines to apportion. Omit for a full restitution.
`deposit`	Yes	Deposit paid at move-in (€).
`lease_type`	No	'vide' unfurnished (deposit cap 1 month) or 'meuble' furnished (cap 2 months). Never presumed: omitted, no cap is computed.
`copropriete`	No	true when the dwelling is in an immeuble collectif (a collective building, co-owned or not): the landlord may keep a duly justified provision of at most 20 % of the deposit until the building's yearly accounts (art. 22, al. 5).
`edl_outcome`	Yes	'identical' when the exit état des lieux matches the entry one (1-month deadline); 'differences' otherwise (2 months).
`perspective`	No	Who is asking — changes only the next_steps wording, never the figures.
`apply_provision`	No	true to deduct provision_amount in the figures; false to leave it out. Without provision_amount nothing can be deducted: the tool asks for the amount.
`key_return_date`	Yes	Date the keys were handed back (remise des clés), ISO date — the deadline runs from this day.
`provision_amount`	No	Immeuble collectif only: the provision the landlord keeps, € — the landlord's own justified amount, at most 20 % of the deposit. Never assumed: omitted, no provision is deducted and the result only states the maximum.
`restitution_date`	No	Date the deposit was / will be returned (ISO) — the penalty is computed against it. Omitted, the figures are computed as of today (date in France) and the result says the date was assumed (as_of.assumed).
`rent_hors_charges`	Yes	Monthly rent en principal, excluding charges (€).
`tenant_gave_address`	No	false when the tenant never gave the address of the new home and the delay results from it — the late penalty is then not due (art. 22, al. 7). Defaults to true.
`provision_justification`	No	What justifies the provision (e.g. 'arrêté provisoire des comptes du 15/09/2026').

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 27, 2026

changedInput schema / properties / apply_provision / description

Previous value: -"true to actually keep the copropriété provision in the figures (default false)."New value: +"true to deduct provision_amount in the figures; false to leave it out. Without provision_amount nothing can be deducted: the tool asks for the amount."

changedInput schema / properties / copropriete / description

Previous value: -"true when the building is a copropriété: the landlord may keep a provision ≤ 20 % of the deposit until the annual charge settlement."New value: +"true when the dwelling is in an immeuble collectif (a collective building, co-owned or not): the landlord may keep a duly justified provision of at most 20 % of the deposit until the building's yearly accounts (art. 22, al. 5)."

changedInput schema / properties / damages / items / properties / age_years / description

Previous value: -"Age of the element in years (installed or last renewed). Defaults to 0."New value: +"Age of the element in years (installed or last renewed) — 0 for a new element. REQUIRED when a grille applies to the line (grille_key, lifespan_years or annual_rate_pct): the chargeable share is computed from it and it is never assumed."

changedInput schema / properties / lease_type / description

Previous value: -"'vide' unfurnished (deposit cap 1 month) or 'meuble' furnished (cap 2 months). Defaults to vide."New value: +"'vide' unfurnished (deposit cap 1 month) or 'meuble' furnished (cap 2 months). Never presumed: omitted, no cap is computed."

addedInput schema / properties / provision_amount

Added value: +{
+  "description": "Immeuble collectif only: the provision the landlord keeps, € — the landlord's own justified amount, at most 20 % of the deposit. Never assumed: omitted, no provision is deducted and the result only states the maximum.",
+  "maximum": 1000000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / provision_justification

Added value: +{
+  "description": "What justifies the provision (e.g. 'arrêté provisoire des comptes du 15/09/2026').",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / restitution_date / description

Previous value: -"Date the deposit was / will be returned (ISO). Defaults to today — the penalty is computed against it."New value: +"Date the deposit was / will be returned (ISO) — the penalty is computed against it. Omitted, the figures are computed as of today (date in France) and the result says the date was assumed (as_of.assumed)."

changedInput schema / properties / tenant_gave_address / description

Previous value: -"false when the tenant never gave a new address — the late penalty is then not due (art. 22). Defaults to true."New value: +"false when the tenant never gave the address of the new home and the delay results from it — the late penalty is then not due (art. 22, al. 7). Defaults to true."

AddedSep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds substantial non-obvious behavior on top: deterministic rules not AI, 'nothing is assumed' with explicit defaults, disclosure that the fallback grille is ILLUSTRATIVE and that no official grille exists, and that the response flags an assumed date (as_of.assumed). This is exactly the kind of context annotations cannot carry.

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?

The critical facts are front-loaded in the first sentence, followed by a denser explanatory paragraph. It is long, and the French-language restatement duplicates the English summary rather than adding information for an agent, which costs a point against strict conciseness.

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?

There is no output schema, so the description must hint at returns, and it does: it names what changes by perspective (next_steps), that the result states the legal maximum, and that an assumed date is surfaced in as_of. For a 13-parameter legal calculator this leaves nothing material an agent needs unstated.

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?

With 100% schema description coverage the baseline is 3, and the description earns above it by adding input-shaping guidance the schema lacks: how to phrase damage items ('what, repair cost, age of the element') and what is deliberately omitted when not supplied (lease type, provision amount). It does not, however, add per-parameter meaning beyond what the schema already documents.

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 opening line names a specific verb-resource pair (deposit restitution) and enumerates the three outputs it produces: due date, late penalty, vétusté-apportioned retentions. It is trivially distinguishable from siblings like calculate_rent_revision or calculate_tenant_notice_period without opening any schema.

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?

The description gives clear operating context: it is for a French residential lease, tells the agent which perspective to pass for landlord vs tenant, and instructs how to elicit inputs ('ask the user for amounts and dates in plain words'). It stops short of naming alternative tools or explicit when-not-to-use conditions, so it is strong but not fully routing.

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 tools Inspect

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

Need Help?