Skip to main content
Glama

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

Assess a tenant application

candidature_locataire
Read-only

QUAND un candidat constitue son dossier pour un logement. Dossier de CANDIDATURE locataire (HTML ; PDF via /api/v1/documents/candidature). Destinataire fenêtre = agence. À classer dans le dossier local après réception.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lieuNoLieu d'établissement du dossier (« Fait à … »).
messageNoMot du candidat à l'agence, ajouté au corps du dossier.
agence_nomNoAgence ou bailleur destinataire du dossier.
garant_nomNoNom du garant, s'il y en a un. La caution se formalise par un acte distinct.
candidat_nomYesNom et prénom du candidat locataire.
candidat_telNoTéléphone du candidat, pour que l'agence puisse le rappeler.
nb_occupantsNoNombre de personnes qui occuperont le logement, enfants compris.
date_emissionNoDate d'établissement, format ISO AAAA-MM-JJ. Par défaut, la date du jour.
situation_proNoSituation professionnelle : CDI, CDD, indépendant, retraité, étudiant. Détermine les pièces attendues.
agence_adresseYesAdresse de l'agence. Sert au bloc fenêtre, poussé À DROITE.
candidat_emailNoAdresse e-mail du candidat.
pieces_jointesNoLibellés des pièces jointes au dossier. ⚠️ Les libellés seulement : ce service ne transporte aucun document.
candidat_adresseNoAdresse actuelle du candidat, avant emménagement.
logement_adresseNoAdresse du logement demandé.
revenus_mensuelsNoRevenus nets mensuels du foyer, en euros. Sert au taux d'effort ; aucun seuil n'est appliqué ici.
reference_annonceNoRéférence de l'annonce, pour rattacher le dossier au bon lot.
date_entree_souhaiteeNoDate d'emménagement souhaitée, format ISO AAAA-MM-JJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / properties / agence_adresse / description
      Added value: +"Adresse de l'agence. Sert au bloc fenêtre, poussé À DROITE."
    • addedInput schema / properties / agence_nom / description
      Added value: +"Agence ou bailleur destinataire du dossier."
    • addedInput schema / properties / candidat_adresse / description
      Added value: +"Adresse actuelle du candidat, avant emménagement."
    • addedInput schema / properties / candidat_email / description
      Added value: +"Adresse e-mail du candidat."
    • addedInput schema / properties / candidat_nom / description
      Added value: +"Nom et prénom du candidat locataire."
    • addedInput schema / properties / candidat_tel / description
      Added value: +"Téléphone du candidat, pour que l'agence puisse le rappeler."
    • addedInput schema / properties / date_emission / description
      Added value: +"Date d'établissement, format ISO AAAA-MM-JJ. Par défaut, la date du jour."
    • addedInput schema / properties / date_entree_souhaitee / description
      Added value: +"Date d'emménagement souhaitée, format ISO AAAA-MM-JJ."
    • addedInput schema / properties / garant_nom / description
      Added value: +"Nom du garant, s'il y en a un. La caution se formalise par un acte distinct."
    • addedInput schema / properties / lieu / description
      Added value: +"Lieu d'établissement du dossier (« Fait à … »)."
    • addedInput schema / properties / logement_adresse / description
      Added value: +"Adresse du logement demandé."
    • addedInput schema / properties / message / description
      Added value: +"Mot du candidat à l'agence, ajouté au corps du dossier."
    • addedInput schema / properties / nb_occupants / description
      Added value: +"Nombre de personnes qui occuperont le logement, enfants compris."
    • addedInput schema / properties / pieces_jointes / description
      Added value: +"Libellés des pièces jointes au dossier. ⚠️ Les libellés seulement : ce service ne transporte aucun document."
    • addedInput schema / properties / reference_annonce / description
      Added value: +"Référence de l'annonce, pour rattacher le dossier au bon lot."
    • addedInput schema / properties / revenus_mensuels / description
      Added value: +"Revenus nets mensuels du foyer, en euros. Sert au taux d'effort ; aucun seuil n'est appliqué ici."
    • addedInput schema / properties / situation_pro / description
      Added value: +"Situation professionnelle : CDI, CDD, indépendant, retraité, étudiant. Détermine les pièces attendues."
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful behavior beyond that: the PDF retrieval route and the instruction to file the result locally ("À classer dans le dossier local après réception"). It does not mention auth, quotas, or error behavior, so it stays at a solid 3.

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?

Four short telegraphic fragments with the usage trigger front-loaded and no filler. It is appropriately sized, though the fragmentary, clipped style slightly reduces readability and structure compared to full sentences.

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 17-parameter tool with no output schema, the description does give the output format and destination, which is the main missing piece. It still omits what the caller receives concretely, where the HTML is written, and any permission or prerequisite context for generating the dossier.

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 17 parameters, including the notable caveat that pieces_jointes carries labels only, not documents. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the explanatory work.

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

Purpose3/5

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

The description identifies the artifact produced ("Dossier de CANDIDATURE locataire") and its formats (HTML, PDF via /api/v1/documents/candidature), but never states the action verb — it is left implicit that the tool generates the dossier. A reader must infer the operation from the artifact name rather than from an explicit verb+resource pairing.

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 front-loaded "QUAND un candidat constitue son dossier pour un logement" gives a clear situational trigger for invocation. However, it names no alternative tool and states no when-not conditions, so routing among the many sibling document tools is still left to inference.

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