Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

quittance_loyer

Generate a legally compliant French rent receipt (quittance de loyer) as printable HTML, formatted for a windowed envelope with the tenant's address on the right.

Instructions

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 (PDF via POST /api/v1/documents/quittance). 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. First observedv1.1.1

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it delivers: HTML printable output, PDF endpoint, envelope layout requirements, address selection rules, and a validation guardrail (refusal without a 5-digit postal code). This is far beyond a minimal 'generate receipt' statement.

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?

Five dense sentences, front-loaded with the critical condition, with no filler. Each sentence covers a distinct operational requirement: trigger, output, layout, address semantics, and guardrail.

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 10-parameter document generator with no annotations and no output schema, the description covers trigger, legal basis, output format, layout, address semantics, and failure condition. The input schema supplies the remaining parameter details, so an agent has enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description reinforces the key distinction between locataire_adresse and logement_adresse and adds the postal-code validation guardrail, but most parameter meaning already lives in the schema.

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 action ('Génère une quittance de loyer conforme') and a precise trigger ('QUAND le loyer a été PAYÉ ... jamais avant encaissement'). The legal reference and output format further pin down the resource, and the condition distinguishes it from payment/reminder tools among siblings.

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?

Explicitly says when to use the tool (tenant paid and requests receipt) and gives a hard exclusion ('jamais avant encaissement'). It does not name alternative sibling tools directly, but the trigger and guardrail make confusion with declaration_paiement or relance_impaye unlikely.

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

Deploy Server

Other Tools