Skip to main content
Glama

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

Draft a rent receipt

quittance_loyer
Read-only

QUAND le loyer a été PAYÉ et que le locataire demande sa quittance — jamais avant encaissement (art. 21). Génère une quittance de loyer conforme (art. 21 loi 89-462), HTML imprimable renvoyé en HTML complet dans la réponse — ni fichier, ni URL, ni PDF, et rien n'est enregistré ni envoyé au locataire. TOUJOURS mis en page pour ENVELOPPE À FENÊTRE : destinataire à DROITE, sans libellé dans la fenêtre. Utilisez locataire_adresse (postale : rue + CP + ville) distincte de logement_adresse (bien loué). Garde-fou : refus si pas de code postal 5 chiffres.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lieuNoLieu d'émission imprimé avant la date (« Fait à … »).
loyerYesLoyer hors charges effectivement encaissé, en euros.
chargesNoProvision pour charges encaissée, en euros. La quittance les distingue du loyer (art. 21, loi 89-462).
periodeYesex. 01/07/2026 au 31/07/2026
bailleur_nomYesBailleur qui délivre la quittance.
date_paiementYesDate de l'encaissement. Format ISO AAAA-MM-JJ. Par défaut, la date du jour.
locataire_nomYesLocataire ayant payé, destinataire de la quittance.
bailleur_adresseNoAdresse du bailleur, en en-tête.
logement_adresseYesAdresse du bien loué (corps du document). Sert de repli postal si locataire_adresse absente.
locataire_adresseNoAdresse POSTALE du locataire (fenêtre d'enveloppe) — ex. "12 rue de la Paix\n75002 Paris". Prioritaire.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / bailleur_adresse / description
      Added value: +"Adresse du bailleur, en en-tête."
    • addedInput schema / properties / bailleur_nom / description
      Added value: +"Bailleur qui délivre la quittance."
    • addedInput schema / properties / charges / description
      Added value: +"Provision pour charges encaissée, en euros. La quittance les distingue du loyer (art. 21, loi 89-462)."
    • addedInput schema / properties / date_paiement / description
      Added value: +"Date de l'encaissement. Format ISO AAAA-MM-JJ. Par défaut, la date du jour."
    • addedInput schema / properties / lieu / description
      Added value: +"Lieu d'émission imprimé avant la date (« Fait à … »)."
    • addedInput schema / properties / locataire_nom / description
      Added value: +"Locataire ayant payé, destinataire de la quittance."
    • addedInput schema / properties / loyer / description
      Added value: +"Loyer hors charges effectivement encaissé, en euros."
  2. Changed2 schema fields changed
    • addedInput schema / properties / locataire_adresse
      Added value: +{
+  "description": "Adresse POSTALE du locataire (fenêtre d'enveloppe) — ex. \"12 rue de la Paix\\n75002 Paris\". Prioritaire.",
+  "type": "string"
+}
    • addedInput schema / properties / logement_adresse / description
      Added value: +"Adresse du bien loué (corps du document). Sert de repli postal si locataire_adresse absente."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only/non-destructive/non-open-world, yet the description adds substantial context beyond them: output is inline full HTML (no file, URL, or PDF), nothing is persisted or sent to the tenant, layout is fixed for a window envelope, and a guardrail rejects requests lacking a 5-digit postal code. This is a genuinely rich behavioral profile consistent with the annotations.

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?

Dense but front-loaded: the trigger/exclusion comes first, then format, layout, parameter guidance, and guardrail in order of importance. Heavy all-caps emphasis and a long single paragraph cost it a point, but essentially every clause carries operational 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, so the description correctly takes on the return contract (complete inline HTML, envelope-ready layout) as well as persistence behavior and refusal conditions. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds real disambiguation: locataire_adresse must be the tenant's postal address distinct from logement_adresse (the rented property), plus the postal-code guardrail constrains the values. It clarifies semantics the schema leaves as overlapping optional fields.

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 (génère une quittance de loyer) and immediately scopes it with the legal basis (art. 21 loi 89-462). An agent can distinguish it from siblings like avis_echeance or regularisation_charges without opening the schema.

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?

Front-loads an explicit trigger ('QUAND le loyer a été PAYÉ et que le locataire demande sa quittance') and an explicit exclusion ('jamais avant encaissement (art. 21)'). The when-not condition is unambiguous, which is rare and exactly what routing needs.

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

All immobilier 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