Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

edl_etat_des_lieux

Generate a legally compliant French inventory of fixtures (état des lieux) for move-in or move-out, documenting room conditions, meter readings, and keys to support security deposit deductions.

Instructions

QUAND il faut constater l'état du logement, à l'entrée ou à la sortie — pièce indispensable pour retenir sur le dépôt de garantie. État des lieux d'entrée ou de sortie (décret 2016-382). PDF via POST /api/v1/documents/edl. pieces[], compteurs[], cles[].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clesNoClés, badges et télécommandes remis, avec leur nombre.
dateNoDate de la visite contradictoire. Format ISO AAAA-MM-JJ. Par défaut, la date du jour.
typeNo« entree » ou « sortie ». La comparaison des deux fonde toute retenue sur le dépôt de garantie.
notesNoObservations ne relevant d'aucune pièce en particulier.
piecesNoPièces visitées, chacune avec l'état constaté de ses sols, murs, plafonds et équipements.
propreteNoÉtat de propreté constaté à la visite.
agent_nomNoPersonne qui conduit l'état des lieux pour le bailleur.
compteursNoRelevés des compteurs au jour de la visite : eau, électricité, gaz.
bailleur_nomYesBailleur présent ou représenté à l'état des lieux.
etat_generalNoAppréciation d'ensemble du logement : neuf, bon, moyen, vétuste.
locataire_nomYesLocataire entrant ou sortant.
bailleur_adresseNoAdresse du bailleur, en en-tête.
logement_adresseNoAdresse du logement visité.
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.9/5.0
Behavior3/5

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

The description mentions 'PDF via POST /api/v1/documents/edl', which implies the tool generates and posts a PDF document. However, it does not disclose any side effects, authentication requirements, rate limits, or potential destructive actions, and no annotations are provided to fill this gap.

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?

The description is concise and front-loads the most important usage condition ('QUAND'). It includes necessary context (legal basis, PDF output) without unnecessary fluff, though it repeats 'État des lieux d'entrée ou de sortie' in a slightly redundant way.

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

Completeness4/5

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

The description provides sufficient context for the tool's role in the rental lifecycle, including its legal basis and its importance for deposit deductions. It also indicates the output format (PDF) and mentions key parameter groups (pieces, compteurs, cles), which helps the agent understand the overall scope even without an output schema.

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?

The schema already provides descriptions for 100% of the parameters, so the baseline is 3. The tool description adds some contextual hints (e.g., 'la comparaison des deux fonde toute retenue') but does not substantially enhance the parameter explanations beyond what the schema already offers.

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?

The description clearly states the tool's purpose: to create an état des lieux (inventory of fixtures) for entering or exiting a rental, and explicitly mentions it is essential for withholding from the security deposit. It is distinct from sibling tools that handle other documents like DXF generation or rent receipts.

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 description explicitly starts with 'QUAND il faut constater l'état du logement, à l'entrée ou à la sortie', giving a clear trigger condition. It also mentions the legal decree (2016-382) and the fact that comparing entry and exit states is the basis for deposit deductions, though it does not explicitly contrast with alternative tools.

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