Skip to main content
Glama
OpenLMNP

OpenLMNP

Update Property

update_property
DestructiveIdempotent

Update selected fields of an existing property record while leaving omitted data unchanged, covering address, area, valuation, DPE, rental, and tax details.

Instructions

Met à jour les champs d'un bien immobilier existant. Seuls les champs fournis sont modifiés. Les montants sont en euros, les surfaces en m². residence_situation : separate, part_of_residence, independent_unit_in_residence. tourism_classification : furnished_tourism_unclassified, furnished_tourism_classified, long_term.

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": {
      "property_id": "<property_id>"
    },
    "name": "update_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoNouvelle ville
nameNoNouveau nom
typeNoType : apartment, house, room, studio, other
notesNoNotes libres
addressNoNouvelle adresse
dpe_classNoClasse du DPE : A à G
dpe_numberNoNuméro du DPE
total_areaNoSurface totale en m²
tva_regimeNoexempt ou liable
agency_feesNoHonoraires agence en euros
notary_feesNoFrais de notaire en euros
postal_codeNoNouveau code postal
property_idYesID du bien à modifier
rental_typeNoseasonal, long_term ou mixed
rented_areaNoSurface louée en m²
market_valueNoValeur de marché en euros
dpe_valid_untilNoDate de fin de validité du DPE (YYYY-MM-DD)
land_percentageNoQuote-part terrain en %
acquisition_dateNoDate d'acquisition (YYYY-MM-DD)
acquisition_priceNoPrix d'acquisition en euros
market_value_dateNoDate d'estimation valeur de marché (YYYY-MM-DD)
rental_start_dateNoDébut du régime réel (YYYY-MM-DD)
dpe_established_atNoDate d'établissement du DPE (YYYY-MM-DD)
activity_start_dateNoPremière mise en location, micro-BIC compris (YYYY-MM-DD) ; chaîne vide pour l'effacer (= rental_start_date)
residence_situationNoseparate, part_of_residence ou independent_unit_in_residence
is_primary_residenceNo⚠️ Déprécié, utiliser residence_situation. Résidence principale
tourism_classificationNoClassement micro-BIC : furnished_tourism_unclassified, furnished_tourism_classified, long_term

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) ; chaîne vide pour l'effacer (= rental_start_date)",
      +  "type": "string"
      +}
    • addedInput schema / properties / address / description
      Added value: +"Nouvelle adresse"
    • addedInput schema / properties / agency_fees / description
      Added value: +"Honoraires agence en euros"
    • addedInput schema / properties / city / description
      Added value: +"Nouvelle 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. Résidence principale"
    • addedInput schema / properties / land_percentage / description
      Added value: +"Quote-part terrain en %"
    • addedInput schema / properties / market_value / description
      Added value: +"Valeur de marché en euros"
    • addedInput schema / properties / market_value_date / description
      Added value: +"Date d'estimation valeur de marché (YYYY-MM-DD)"
    • addedInput schema / properties / name / description
      Added value: +"Nouveau nom"
    • 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: +"Nouveau code postal"
    • addedInput schema / properties / property_id / description
      Added value: +"ID du bien à modifier"
    • addedInput schema / properties / rental_start_date / description
      Added value: +"Début du régime réel (YYYY-MM-DD)"
    • addedInput schema / properties / rental_type / description
      Added value: +"seasonal, long_term ou mixed"
    • addedInput schema / properties / rented_area / description
      Added value: +"Surface louée en m²"
    • addedInput schema / properties / residence_situation
      Added value: +{
      +  "description": "separate, part_of_residence ou 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, furnished_tourism_classified, long_term",
      +  "type": "string"
      +}
    • addedInput schema / properties / tva_regime / description
      Added value: +"exempt ou liable"
    • addedInput schema / properties / type / description
      Added value: +"Type : apartment, house, room, studio, other"
  2. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is covered. The description adds real value by disclosing partial-update behavior and units (euros, m²), but it never warns that supplied values overwrite existing ones (consistent with destructiveHint) and says nothing about failure behavior for an unknown property_id.

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 sentences, front-loaded with the core action and patch semantics before the unit and value-list details. Minor redundancy with the schema's own unit and enum text keeps it from a 5.

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 27-parameter mutation tool with no output schema, the definition covers the essential contract but leaves gaps: the return value after update is unspecified, and special cases such as passing an empty string to clear activity_start_date are only in the schema. Given the rich schema, the remaining burden on the description is modest but not fully met.

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%, so all 27 parameters are already documented, making 3 the baseline. The description restates the currency and area units and repeats the allowed values for residence_situation and tourism_classification, which is mildly useful since no parameters are structurally enumerated, but it adds no meaning beyond the schema, and it omits the deprecated is_primary_residence note that the schema carries.

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?

States a specific verb and resource ('Met à jour les champs d'un bien immobilier existant') and adds the patch qualifier 'Seuls les champs fournis sont modifiés', which distinguishes it from create_property. It does not name any sibling (e.g. update_property_work) to draw a boundary, so it stops short of a 5.

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

Usage Guidelines3/5

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

The patch semantics ('only provided fields are modified') give an implicit cue for when to use this rather than a full-replacement call. However, there is no explicit when/when-not guidance, no mention of the related update_property_work or create_property siblings, and no stated prerequisite that the property_id must already exist.

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