Skip to main content
Glama

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

Draft a rental listing

annonce_location
Read-only

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: /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. Changed14 schema fields changed
    • addedInput schema / properties / agence_nom / description
      Added value: +"Agence ou bailleur qui publie."
    • addedInput schema / properties / charges / description
      Added value: +"Provision mensuelle pour charges, en euros. Doit etre affichee separement du loyer."
    • addedInput schema / properties / code_postal / description
      Added value: +"Code postal, cinq chiffres."
    • addedInput schema / properties / contact / description
      Added value: +"Coordonnees de visite affichees dans l'annonce."
    • addedInput schema / properties / description / description
      Added value: +"Texte descriptif du bien : agencement, exposition, equipements, transports."
    • changedInput schema / properties / dpe / description
      Previous value: -"Classe DPE A–G"New value: +"Classe 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."
    • addedInput schema / properties / loyer / description
      Added value: +"Loyer mensuel hors charges, en euros. ATTENTION : en zone tendue l'encadrement des loyers s'applique et n'est PAS verifie ici."
    • addedInput schema / properties / nb_pieces / description
      Added value: +"Nombre de pieces principales, cuisine et salle d'eau exclues."
    • addedInput schema / properties / reference / description
      Added value: +"Reference interne de l'annonce, pour rattacher les candidatures recues."
    • addedInput schema / properties / statut / description
      Added value: +"Toujours « brouillon » : ce service REDIGE l'annonce, il ne la publie nulle part. La diffusion reste un geste humain."
    • addedInput schema / properties / surface_m2 / description
      Added value: +"Surface habitable en m2, au sens de la loi Carrez ou Boutin selon le bail."
    • addedInput schema / properties / titre / description
      Added value: +"Accroche de l'annonce. Laissee vide, elle est composee a partir du type, de la surface et de la ville."
    • addedInput schema / properties / type_bien / description
      Added value: +"Nature du bien : studio, appartement, maison, local commercial, parking."
    • addedInput schema / properties / ville / description
      Added value: +"Commune du bien."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, and the description adds genuinely non-derivable behavior: the output is a draft only, no listing is ever published through MCP, publication is reserved for the Synergieloc operator via manual validation, and publier=true is rejected. It also cites the backing REST route, which helps the agent understand the call's scope.

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?

Front-loaded with the trigger condition, then the action, then the critical constraint. Slight redundancy between 'aucune publication sur synergieloc.fr via MCP' and 'publier=true est refusé', though the emphasis is defensible for a constraint that must not be missed. Four sentences, no filler.

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?

With 14 optional parameters and no output schema, the description compensates by naming the return shape (texte_brut + html) and by explaining the statut='brouillon' constraint that governs the whole call. Nothing needed to invoke it correctly is missing.

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% across all 14 parameters, and those descriptions already carry the substantive semantics (DPE classes A-G with F/G restrictions, loyer hors charges with rent-control caveat, statut fixed to 'brouillon'). The description adds no per-parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 verb and resource ('Rédige un BROUILLON d'annonce de location') plus the exact output form (texte_brut + html). It also draws a sharp line between drafting and publishing, so an agent can tell it apart from any diffusion/publishing path in the sibling set (mandat_gerance, candidature_locataire).

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?

Opens with an explicit trigger condition ('QUAND un bien vacant doit être mis en location et qu'il faut rédiger l'annonce') and an explicit exclusion (no publication via MCP, publier=true refused). It does not name a sibling alternative, but the when-to-use and when-not-to-use conditions are both stated directly.

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

All immobilier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources