Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

avenant_revision_irl

Generate a tenant notification letter for French IRL rent revision, formatted for window envelopes with printable HTML and PDF export.

Instructions

QUAND la révision IRL est calculée et qu'il faut la NOTIFIER au locataire par courrier. Calculez d'abord avec irl_revision_loyer. Courrier de révision de loyer IRL prêt à envoyer au locataire (HTML imprimable ; PDF via /api/v1/documents/avenant-irl). Calcule et notifie le nouveau loyer. TOUJOURS mis en page pour ENVELOPPE À FENÊTRE (destinataire à DROITE). Preférer locataire_adresse (postale) ≠ logement_adresse (bien). Garde-fou : code postal 5 chiffres obligatoire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lieuNoLieu d'émission imprimé avant la date (« Fait à … »).
date_effetYesDate d'application du nouveau loyer. Format ISO AAAA-MM-JJ. Par défaut, la date du jour. La révision ne rétroagit pas au-delà d'un an (art. 17-1, loi 89-462).
irl_nouveauYesValeur de l'IRL du même trimestre, publiée par l'INSEE cette année.
bailleur_nomYesBailleur qui notifie la révision.
loyer_actuelYesLoyer hors charges en vigueur avant révision, en euros.
irl_referenceYesValeur de l'IRL du trimestre de référence inscrit au bail.
locataire_nomYesLocataire destinataire de la notification.
bailleur_adresseNoAdresse du bailleur, en en-tête.
logement_adresseYesAdresse du bien loué (objet du courrier).
locataire_adresseNoAdresse POSTALE du locataire (fenêtre) — ex. "12 rue de la Paix\n75002 Paris".
trimestre_nouveauNoTrimestre correspondant de l'année en cours — « T2 2026 ».
trimestre_referenceNoTrimestre de référence du bail — « T2 2025 ». C'est le bail qui le fixe, pas l'usage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the result is a ready-to-send letter rather than an actual send ('Courrier ... prêt à envoyer' vs 'notifie'), and reveals the always-on window-envelope layout and PDF endpoint. It also surfaces a 5-digit postal-code validation that an agent would otherwise only discover at runtime.

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?

Each clause carries distinct information: trigger, prerequisite, output, envelope constraint, address preference, and validation rule. The trigger is front-loaded, there is no filler, and the length is proportionate to a 12-parameter document-generation 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 document-generation tool with no output schema or annotations, the description explains when to use it, what it produces (HTML and PDF via endpoint), input preferences, and a key validation rule. It also names the calculation sibling tool so the agent can orchestrate the workflow correctly; nothing essential 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?

The input schema already covers 100% of the 12 parameters, so the baseline is 3. The description adds actionable semantics beyond the schema: prefer locataire_adresse (postal) over logement_adresse (property) for the window, and enforce a 5-digit postal code. This improves correct parameter population.

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 precise action: notify the tenant of an IRL rent revision via a ready-to-send letter. It identifies the resource ('Courrier de révision de loyer IRL'), the output formats (HTML/PDF), and explicitly distinguishes it from irl_revision_loyer, whose calculation must precede this tool.

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?

Opens with an explicit 'QUAND' condition (revision already calculated, need to notify tenant by mail) and instructs to calculate with irl_revision_loyer first. It also gives address-choice guidance (postal address vs property address) and a mandatory postal-code guardrail, leaving no doubt when to invoke this tool.

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