Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

annonce_location

Generate a draft French rental listing for a vacant property, including mandatory DPE class and separate charges. Outputs plain text and HTML; never publishes.

Instructions

QUAND un bien vacant doit être mis en location et qu'il faut rédiger l'annonce. Rédige un BROUILLON d'annonce de location (texte_brut + html). IMPORTANT : aucune publication sur synergieloc.fr via MCP — la mise en ligne est réservée à l'opérateur Synergieloc (validation manuelle uniquement). publier=true est refusé. REST: POST /api/v1/gerance/annonce-location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpeNoClasse du diagnostic de performance energetique, de A a G. Mention OBLIGATOIRE dans toute annonce de location ; les classes F et G sont soumises a restrictions.
loyerNoLoyer mensuel hors charges, en euros. ATTENTION : en zone tendue l'encadrement des loyers s'applique et n'est PAS verifie ici.
titreNoAccroche de l'annonce. Laissee vide, elle est composee a partir du type, de la surface et de la ville.
villeNoCommune du bien.
statutNoToujours « brouillon » : ce service REDIGE l'annonce, il ne la publie nulle part. La diffusion reste un geste humain.brouillon
chargesNoProvision mensuelle pour charges, en euros. Doit etre affichee separement du loyer.
contactNoCoordonnees de visite affichees dans l'annonce.
nb_piecesNoNombre de pieces principales, cuisine et salle d'eau exclues.
referenceNoReference interne de l'annonce, pour rattacher les candidatures recues.
type_bienNoNature du bien : studio, appartement, maison, local commercial, parking.
agence_nomNoAgence ou bailleur qui publie.
surface_m2NoSurface habitable en m2, au sens de la loi Carrez ou Boutin selon le bail.
code_postalNoCode postal, cinq chiffres.
descriptionNoTexte descriptif du bien : agencement, exposition, equipements, transports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.3/5.0
Behavior5/5

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

The description explicitly discloses a critical behavioral constraint: it refuses publication (publier=true est refusé) and only produces a draft. This is reinforced by the schema's statut enum limited to 'brouillon'. No annotations exist to carry this burden, so the description does it thoroughly.

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 well-structured: a trigger clause, an action clause, and a clear constraint. It avoids redundancy with the schema and is not overly verbose.

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 covers the tool's purpose, output format (texte_brut + html), and the crucial non-publication constraint. It does not enumerate all parameters, but the schema covers them. Given the complexity and lack of annotations, the context is sufficiently complete.

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 100% coverage with detailed descriptions for all 14 parameters. The tool description adds no additional parameter-level semantics, so the baseline of 3 is appropriate.

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 drafts a rental listing (brouillon) when a vacant property needs an ad. It also distinguishes itself by explicitly stating it never publishes, which is a key differentiator from other tools.

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 provides a clear trigger condition ('QUAND un bien vacant doit être mis en location') and explicitly states the service only drafts, never publishes, which guides when to use it. It could name alternative tools, but the condition is sufficient.

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