Skip to main content
Glama
OpenLMNP

OpenLMNP

Update Property Work

update_property_work
DestructiveIdempotent

Update an existing property work record with partial fields such as amount, VAT rate, date, description, dedicated status, or duration; recalculates annual depreciation when amount or duration changes.

Instructions

Met à jour un poste de travaux immobiliers existant. Seuls les champs fournis sont modifiés (mise à jour partielle). Le montant est en euros. L'amortissement annuel est recalculé automatiquement si le montant ou la durée changent.

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": {
      "work_id": "<work_id>"
    },
    "name": "update_property_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoMontant TTC en euros
work_idYesIdentifiant des travaux à mettre à jour
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%)
work_dateNoDate des travaux au format Y-m-d
descriptionNoNouvelle description
is_dedicatedNoTravaux 100% dédiés à la location
duration_yearsNoDurée d'amortissement en années

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.1
    • addedInput schema / properties / amount / description
      Added value: +"Montant TTC en euros"
    • addedInput schema / properties / description / description
      Added value: +"Nouvelle description"
    • addedInput schema / properties / duration_years / description
      Added value: +"Durée d'amortissement en années"
    • addedInput schema / properties / is_dedicated / description
      Added value: +"Travaux 100% dédiés à la location"
    • addedInput schema / properties / tva_rate / description
      Added value: +"Taux de TVA en pourcentage (ex: 20 pour 20%)"
    • addedInput schema / properties / work_date / description
      Added value: +"Date des travaux au format Y-m-d"
    • addedInput schema / properties / work_id / description
      Added value: +"Identifiant des travaux à mettre à jour"
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare idempotentHint and destructiveHint, so the description's disclosure that annual depreciation is automatically recalculated when amount or duration changes is real added behavioral value — an agent would not otherwise know about this side effect. It also states the currency basis (euros). It stops short of saying whether the recalculated depreciation is returned in the response or whether the recalculation can be undone.

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 action and immediately followed by the partial-update contract and the recalculation side effect. No filler or repetition; the only mild redundancy is restating the euro currency already present in the schema.

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?

For a 7-parameter mutation tool with full schema coverage and annotations covering safety, the description covers the key unknowns: partial-update semantics and the automatic depreciation recalculation. Since there is no output schema, one would ideally want to know what the response contains after recalculation, which is the remaining gap.

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 every parameter is already documented, which sets the baseline at 3. The description adds only marginal meaning: the euro denomination (already in the amount field description) and the linkage between amount/duration_years and the depreciation recomputation, without elaborating on tva_rate or is_dedicated semantics.

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?

The description opens with a specific verb and resource ("Met à jour un poste de travaux immobiliers existant"), making clear this mutates an existing property work item rather than creating or deleting one. It does not explicitly name the sibling create_property_work or delete_property_work, but the "existant" qualifier plus the required work_id makes the boundary inferable.

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 partial-update rule ("Seuls les champs fournis sont modifiés") is genuinely useful usage guidance because it tells the agent it need not resend the full record. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as create_property_work for new items or the depreciation compute tools for read-only recalculation.

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