Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mouvement_locataire

Generate a French rental move-in or move-out checklist with final settlement, covering security deposit deductions, meter readings, keys, and handover dates.

Instructions

QUAND un locataire ENTRE ou SORT du logement : checklist et solde de tout compte. Document ENTRÉE ou SORTIE locataire (checklist + solde de tout compte). PDF via POST /api/v1/documents/mouvement-locataire. type=entree|sortie.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lieuNoLieu d'établissement imprimé avant la date (« Fait à … »).
typeYesSens du mouvement : « entree » ou « sortie ». Il détermine les rubriques imprimées.
retenuesNoRetenues opérées sur le dépôt, chacune justifiée. Une retenue sans justificatif se conteste.
checklistNoPoints à vérifier lors du mouvement : compteurs, clés, boîte aux lettres, assurance.
date_effetNoDate d'entrée ou de sortie effective. Format ISO AAAA-MM-JJ. Par défaut, la date du jour.
bailleur_nomYesBailleur du logement concerné.
solde_lignesNoLignes du solde de tout compte, chacune avec son libellé et son montant en euros.
date_emissionNoFormat ISO AAAA-MM-JJ. Par défaut, la date du jour.
locataire_nomYesLocataire qui entre ou qui sort.
depot_garantieNoDépôt de garantie versé à l'entrée, en euros. Sa restitution court à compter de la remise des clés.
bailleur_adresseNoAdresse du bailleur, en en-tête.
logement_adresseNoAdresse du logement concerné par le mouvement.
locataire_adresseNoAdresse du destinataire. Sert au bloc fenêtre : il est poussé À DROITE pour une enveloppe à fenêtre.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does add useful behavioral context: 'PDF via POST /api/v1/documents/mouvement-locataire' reveals the output format and signals a side-effectful creation operation. It remains silent on authentication, whether the PDF is returned directly or stored, and any limits, which prevents a higher score.

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 trigger condition is front-loaded in uppercase, which is structurally sound. But the first two sentences are near-duplicates ('QUAND un locataire ENTRE ou SORT... checklist et solde de tout compte' vs. 'Document ENTRÉE ou SORTIE locataire (checklist + solde de tout compte)'), and 'type=entree|sortie' repeats the schema enum, so not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no annotations and no output schema, the description covers the essential trigger, the two mode variants, and the PDF output, which is adequate but minimal. It does not clarify the boundary with edl_etat_des_lieux nor what happens after generation (download, storage, listing), leaving an agent to infer operational details.

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 schema fully documents all 13 parameters and the baseline is 3. The description's 'type=entree|sortie' and 'checklist + solde de tout compte' merely restate what the schema already says and add no new parameter-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action — producing a tenant entry/exit document (checklist + solde de tout compte) — with the trigger condition front-loaded ('QUAND un locataire ENTRE ou SORT du logement'). The content spec ('checklist + solde de tout compte') functionally distinguishes it from siblings like edl_etat_des_lieux, but no sibling is explicitly named, so it stops short of a 5.

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 opening 'QUAND un locataire ENTRE ou SORT du logement' is an explicit when-condition, which is clear context for selecting the tool. However, it offers no exclusions or alternatives — notably it never contrasts itself with the closely related edl_etat_des_lieux — so the when-not half of the guidance is absent.

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