Skip to main content
Glama
OpenLMNP

OpenLMNP

Create Property

create_property
Destructive

Register a new LMNP rental property with its acquisition details, surfaces, and tax parameters so you can track income, expenses, and depreciation.

Instructions

Crée un nouveau bien immobilier LMNP pour l'utilisateur connecté. Les montants (acquisition_price, notary_fees, market_value) sont en euros. Les surfaces (total_area, rented_area) sont en m². Type : apartment, house, room, studio, other. Rental type : seasonal, long_term, mixed. TVA : exempt, liable. residence_situation : separate (logement distinct), part_of_residence (pièce(s) de la résidence principale), independent_unit_in_residence (logement indépendant dans la résidence principale ou sur la même propriété — pas de limite de 120 jours, pas d'art. 35 bis, CFE due en principe). tourism_classification : furnished_tourism_unclassified (30 %), furnished_tourism_classified (50 %), long_term (50 %) — abattement micro-BIC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "total_area": "<total_area>",
      "rented_area": "<rented_area>",
      "acquisition_date": "<acquisition_date>",
      "acquisition_price": "<acquisition_price>"
    },
    "name": "create_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoVille
nameYesNom du bien (ex : La Bastide)
typeNoType : apartment, house, room, studio, other
notesNoNotes libres
addressNoAdresse
dpe_classNoClasse du DPE : A à G
dpe_numberNoNuméro du DPE
total_areaYesSurface totale en m²
tva_regimeNoRégime TVA : exempt, liable
agency_feesNoHonoraires agence en euros
notary_feesNoFrais de notaire en euros
postal_codeNoCode postal
rental_typeNoType de location : seasonal, long_term, mixed
rented_areaYesSurface louée en m²
market_valueNoValeur de marché actuelle en euros
dpe_valid_untilNoDate de fin de validité du DPE (YYYY-MM-DD)
land_percentageNoQuote-part terrain non amortissable en % (défaut : 15)
acquisition_dateYesDate d'acquisition (YYYY-MM-DD)
acquisition_priceYesPrix d'acquisition en euros
market_value_dateNoDate d'estimation de la valeur de marché (YYYY-MM-DD)
rental_start_dateNoDébut du régime réel (YYYY-MM-DD) : ouverture du premier exercice au réel. Défaut : date d'acquisition
dpe_established_atNoDate d'établissement du DPE (YYYY-MM-DD)
activity_start_dateNoPremière mise en location, micro-BIC compris (YYYY-MM-DD). À renseigner seulement si le bien a été loué au micro-BIC avant le réel : les annuités de ces années sont réputées pratiquées (dans le cumul, jamais déduites). Vide = rental_start_date
residence_situationNoSituation : separate, part_of_residence, independent_unit_in_residence
is_primary_residenceNo⚠️ Déprécié, utiliser residence_situation. Fait partie de la résidence principale
tourism_classificationNoClassement micro-BIC : furnished_tourism_unclassified (30 %), furnished_tourism_classified (50 %), long_term (50 %). Défaut dérivé de rental_type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv2.0.1
    • addedInput schema / properties / acquisition_date / description
      Added value: +"Date d'acquisition (YYYY-MM-DD)"
    • addedInput schema / properties / acquisition_price / description
      Added value: +"Prix d'acquisition en euros"
    • addedInput schema / properties / activity_start_date
      Added value: +{
      +  "description": "Première mise en location, micro-BIC compris (YYYY-MM-DD). À renseigner seulement si le bien a été loué au micro-BIC avant le réel : les annuités de ces années sont réputées pratiquées (dans le cumul, jamais déduites). Vide = rental_start_date",
      +  "type": "string"
      +}
    • addedInput schema / properties / address / description
      Added value: +"Adresse"
    • addedInput schema / properties / agency_fees / description
      Added value: +"Honoraires agence en euros"
    • addedInput schema / properties / city / description
      Added value: +"Ville"
    • addedInput schema / properties / dpe_class
      Added value: +{
      +  "description": "Classe du DPE : A à G",
      +  "type": "string"
      +}
    • addedInput schema / properties / dpe_established_at
      Added value: +{
      +  "description": "Date d'établissement du DPE (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / dpe_number
      Added value: +{
      +  "description": "Numéro du DPE",
      +  "type": "string"
      +}
    • addedInput schema / properties / dpe_valid_until
      Added value: +{
      +  "description": "Date de fin de validité du DPE (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / is_primary_residence / description
      Added value: +"⚠️ Déprécié, utiliser residence_situation. Fait partie de la résidence principale"
    • addedInput schema / properties / land_percentage / description
      Added value: +"Quote-part terrain non amortissable en % (défaut : 15)"
    • addedInput schema / properties / market_value / description
      Added value: +"Valeur de marché actuelle en euros"
    • addedInput schema / properties / market_value_date / description
      Added value: +"Date d'estimation de la valeur de marché (YYYY-MM-DD)"
    • addedInput schema / properties / name / description
      Added value: +"Nom du bien (ex : La Bastide)"
    • addedInput schema / properties / notary_fees / description
      Added value: +"Frais de notaire en euros"
    • addedInput schema / properties / notes / description
      Added value: +"Notes libres"
    • addedInput schema / properties / postal_code / description
      Added value: +"Code postal"
    • addedInput schema / properties / rental_start_date / description
      Added value: +"Début du régime réel (YYYY-MM-DD) : ouverture du premier exercice au réel. Défaut : date d'acquisition"
    • addedInput schema / properties / rental_type / description
      Added value: +"Type de location : seasonal, long_term, mixed"
    • addedInput schema / properties / rented_area / description
      Added value: +"Surface louée en m²"
    • addedInput schema / properties / residence_situation
      Added value: +{
      +  "description": "Situation : separate, part_of_residence, independent_unit_in_residence",
      +  "type": "string"
      +}
    • addedInput schema / properties / total_area / description
      Added value: +"Surface totale en m²"
    • addedInput schema / properties / tourism_classification
      Added value: +{
      +  "description": "Classement micro-BIC : furnished_tourism_unclassified (30 %), furnished_tourism_classified (50 %), long_term (50 %). Défaut dérivé de rental_type.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tva_regime / description
      Added value: +"Régime TVA : exempt, liable"
    • addedInput schema / properties / type / description
      Added value: +"Type : apartment, house, room, studio, other"
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "acquisition_date",
      -  "acquisition_price"
      -]New value: +[
      +  "name",
      +  "total_area",
      +  "rented_area",
      +  "acquisition_date",
      +  "acquisition_price"
      +]
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The only annotation is destructiveHint=true, so it carries little disclosure burden; the description usefully clarifies that the property belongs to the authenticated user and encodes domain rules (120-day limit, art. 35 bis, CFE, micro-BIC abattement rates). However it never says whether a created object/id is returned (no output schema), whether creation triggers derived computations, or what happens on conflicting input.

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?

Purpose and units are front-loaded, which is good, but the remainder is a dense run-on dump of enum values with semicolon-separated tax notes that duplicates much of the schema and lacks any structural separation. Some sentences (the units line) repeat what schema property descriptions already say.

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 26-parameter creation tool with no output schema and minimal annotations, the description covers purpose, units, enum semantics and default derivation rules, but omits what is returned on success, error behavior, and validation constraints beyond required fields. Adequate but with clear gaps for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the terse schema strings: it states units for amounts (euros) and surfaces (m²) and expands residence_situation and tourism_classification into their legal/tax consequences. Several enumerations (type, rental_type, tva_regime) are simply restated from the schema, so it is not fully additive.

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?

"Crée un nouveau bien immobilier LMNP pour l'utilisateur connecté" gives a specific verb and resource plus the ownership scope, so it is clearly distinguishable from update_property. It stops short of naming an alternative or stating the boundary with the update/sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "nouveau" implies this is for first-time creation and update_property is the alternative, but the description never says so, nor does it state prerequisites (mandatory fields, what to do if the property already exists, whether a duplicate name is allowed). No when-not guidance at all.

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