french-rental-compliance

Generate a French rent receipt (quittance de loyer) PDF — free, no account

generate_rent_receipt

FREE — no account needed. · GRATUIT, sans compte : quittance de loyer en PDF. — Rent receipt (quittance de loyer, loi n° 89-462 art. 21) PDF from the data you give: landlord, tenant, property address, period, rent and charges, payment date. Deterministic template engine — a fixed legal template filled with the given data, not AI-generated content. The document is issued in FRENCH (required for legal validity); includeEnglish appends a non-binding English reference translation. Nothing is stored: the PDF is available for 24 hours through a single-use link, then deleted — no account, no property, no history. Per-network caps apply (a structured rate_limited result says when to retry). Have the landlord verify every field before sending it to the tenant. BLANK MENTIONS: what is not given is printed blank, never invented. Before the document is produced, the tool answers needs_input with blank_mentions — the mentions that would be blank, as printed: show the landlord the list and complete them, or pass acknowledge_incomplete: true once the landlord has chosen to leave them blank. A generated document returns printed_blank, the mentions to complete by hand. With an AdminLanding account the same receipt is pre-filled from your saved properties, the tenant is stamped from the record so their name never passes through the assistant, receipts are kept in your history and shared through the tenant portal, and leases can be sent for e-signature — €4.90 — one document for this property (buy in the web app), or Membership — €6 a month or €59 a year, renewed automatically, cancel any time from the account: every rental document on up to 10 properties (€1 a month or €10 a year per extra property), plus home employment, cross-border, letters and patrimoine; first property free (10 documents). Payment happens in the browser, never through the agent. General information/document tooling, not legal advice.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Filename/interface language only — the document is always issued in French (required for validity). Default fr.
`issuedAt`	No	City where the receipt is issued, printed « Fait à … ». Ask the landlord — it is never taken from an address. Omitted, the mention is blank. The date next to it is the day of issue (today, date in France).
`periodTo`	Yes	Rental period end (ISO date). The receipt month is derived from this date.
`periodFrom`	Yes	Rental period start (ISO date, e.g. 2026-08-01).
`rentAmount`	Yes	Rent RECEIVED, excluding charges, in euros, as a string (e.g. '850' or '850.50'). Above 0: a receipt of nothing is refused.
`tenantName`	Yes	Tenant's full name (locataire) as it must appear on the receipt.
`paymentDate`	Yes	Date the landlord RECEIVED the payment (ISO date).
`landlordName`	Yes	Landlord's full name, or the company's name (bailleur). With an account, a company is designated from the landlord profile — « (société) », SIRET — when this name is the profile's; without one, write the designation here.
`chargesAmount`	Yes	Charges (provisions/forfait), in euros, as a string ('0' if none).
`paymentMethod`	No	Payment method as the landlord states it (e.g. 'Virement bancaire', 'Chèque'), printed after « Mode de paiement ». NO default: omitted, the mention is blank. Never guess it.
`includeEnglish`	No	Append a non-binding English reference translation as the last page. The legal document itself stays French.
`landlordAddress`	Yes	Landlord's address.
`propertyAddress`	Yes	Address of the rented dwelling.
`acknowledge_incomplete`	No	Set ONLY after the tool has returned status:'needs_input' — with blank_mentions, the mentions the document would print blank — you have shown the landlord that list, and the landlord has explicitly chosen to generate the document with those mentions left blank, to complete them by hand before signing or sending. Never set this on a first call. It never waives a refusal: a missing mandatory input, an unlawful value or an input that would not be printed stays refused.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 27, 2026

addedInput schema / properties / acknowledge_incomplete

Added value: +{
+  "description": "Set ONLY after the tool has returned status:'needs_input' — with blank_mentions, the mentions the document would print blank — you have shown the landlord that list, and the landlord has explicitly chosen to generate the document with those mentions left blank, to complete them by hand before signing or sending. Never set this on a first call. It never waives a refusal: a missing mandatory input, an unlawful value or an input that would not be printed stays refused.",
+  "type": "boolean"
+}

addedInput schema / properties / issuedAt

Added value: +{
+  "description": "City where the receipt is issued, printed « Fait à … ». Ask the landlord — it is never taken from an address. Omitted, the mention is blank. The date next to it is the day of issue (today, date in France).",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / landlordName / description

Previous value: -"Landlord's full name (bailleur)."New value: +"Landlord's full name, or the company's name (bailleur). With an account, a company is designated from the landlord profile — « (société) », SIRET — when this name is the profile's; without one, write the designation here."

changedInput schema / properties / paymentMethod / description

Previous value: -"Payment method (e.g. 'Virement bancaire', 'Chèque'). Defaults to bank transfer."New value: +"Payment method as the landlord states it (e.g. 'Virement bancaire', 'Chèque'), printed after « Mode de paiement ». NO default: omitted, the mention is blank. Never guess it."

changedInput schema / properties / rentAmount / description

Previous value: -"Rent excluding charges, in euros, as a string (e.g. '850' or '850.50')."New value: +"Rent RECEIVED, excluding charges, in euros, as a string (e.g. '850' or '850.50'). Above 0: a receipt of nothing is refused."

AddedSep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description supplies the missing behavioral detail: the PDF lives 24 hours behind a single-use link then is deleted, per-network rate caps return a structured rate_limited result with retry guidance, missing mentions print blank and are never invented, and refusals persist even with acknowledge_incomplete. That is far beyond what the annotations state.

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 critical information (free, French-only output, blank mentions, needs_input flow) is front-loaded, but the description is very long and its account/membership paragraph is dense commercial detail (€4.90, €6/month, €59/year, 10 properties, extra-property rates, e-signature) that contributes little to selecting or correctly invoking the tool.

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 14-parameter tool with no output schema, the description closes the important gaps: it names the interactive return states the agent must handle (needs_input/blank_mentions, printed_blank, rate_limited), the 24-hour link lifetime, and the mandatory-French constraint. No output schema exists, so the return-value explanation it does provide is warranted.

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 description coverage is already 100%, so baseline would be 3; the description nonetheless adds cross-parameter semantics the schema cannot express — omitted mentions become printed blanks, includeEnglish only appends a non-binding translation while the document stays French, and acknowledge_incomplete is meaningful only after a needs_input response. It does not add format examples beyond the schema's own patterns.

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 artifact: produce a French rent receipt (quittance de loyer) PDF from supplied landlord/tenant/period/rent data. The legal frame (loi n° 89-462 art. 21) and 'deterministic template engine, not AI-generated' pin down exactly what is produced, which is distinguishable from the calculation-only siblings that merely compute amounts or eligibility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit operating conditions: have the landlord verify every field, payment happens in the browser never through the agent, and the acknowledge_incomplete flag must never be set on a first call — only after a needs_input response has been shown to the landlord. It also describes the account-based variant and pricing path, so an agent knows both the free flow and when the paid one applies.

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?