Skip to main content
Glama

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 month started, none if the tenant gave no new address), the copropriété provision cap (20 %), the legal deposit cap (1 month unfurnished / 2 months furnished) 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). 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
NameRequiredDescriptionDefault
damagesNoDamage lines to apportion. Omit for a full restitution.
depositYesDeposit paid at move-in (€).
lease_typeNo'vide' unfurnished (deposit cap 1 month) or 'meuble' furnished (cap 2 months). Defaults to vide.
coproprieteNotrue when the building is a copropriété: the landlord may keep a provision ≤ 20 % of the deposit until the annual charge settlement.
edl_outcomeYes'identical' when the exit état des lieux matches the entry one (1-month deadline); 'differences' otherwise (2 months).
perspectiveNoWho is asking — changes only the next_steps wording, never the figures.
apply_provisionNotrue to actually keep the copropriété provision in the figures (default false).
key_return_dateYesDate the keys were handed back (remise des clés), ISO date — the deadline runs from this day.
restitution_dateNoDate the deposit was / will be returned (ISO). Defaults to today — the penalty is computed against it.
rent_hors_chargesYesMonthly rent en principal, excluding charges (€).
tenant_gave_addressNofalse when the tenant never gave a new address — the late penalty is then not due (art. 22). Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses that the tool is deterministic rather than AI, that the same figures are returned regardless of perspective (landlord/tenant) with only next_steps changing, that the grille is illustrative when no lease grille exists, and that output is general information, not legal advice.

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 dense but every clause earns its place: key legal figures, statutory basis, caveats about the missing official grille, perspective behavior, input guidance, and disclaimer. The most decision-relevant information is front-loaded in the first sentence.

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?

For a complex 11-parameter tool with no output schema, the description covers the legal rules, edge cases, perspective behavior, and the illustrative-grille caveat. It gives an agent enough context to invoke the tool correctly and set user expectations about the response.

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?

The input schema already covers all 11 parameters at 100%, so the baseline is 3. The description adds meaningful context beyond the schema: deadline depends on edl_outcome, penalty depends on tenant_gave_address, perspective never changes figures, and damage items should be expressed as 'what, repair cost, age of the element'.

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 and resource: calculating French security-deposit restitution, including due date, late penalty, and vétusté-apportioned retentions. It clearly distinguishes itself from sibling tools like rent revision or notice-period calculators by naming its exact legal context (loi n° 89-462 art. 22/25-6) and calculation scope.

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 explicitly frames when the tool applies: a French residential lease with a security deposit, and what inputs the user should provide. It does not name sibling tools as alternatives or give explicit 'do not use when' conditions, but the legal and factual context is specific enough for an agent to route correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources