Skip to main content
Glama
OpenLMNP

OpenLMNP

Update Furniture

update_furniture
DestructiveIdempotent

Update an existing furniture item's amount, VAT, or depreciation period for LMNP accounting; only supplied fields change and annual depreciation recalculates if amount or duration changes.

Instructions

Met à jour un élément de mobilier 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": {
      "furniture_id": "<furniture_id>"
    },
    "name": "update_furniture"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoMontant TTC en euros
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%)
descriptionNoNouvelle description
furniture_idYesIdentifiant du mobilier à mettre à jour
is_dedicatedNoMobilier 100% dédié à la location
purchase_dateNoDate d'achat au format Y-m-d
duration_yearsNoDurée d'amortissement en années
is_second_handNoMobilier d'occasion

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / furniture_id / description
      Added value: +"Identifiant du mobilier à mettre à jour"
    • addedInput schema / properties / is_dedicated / description
      Added value: +"Mobilier 100% dédié à la location"
    • addedInput schema / properties / is_second_hand / description
      Added value: +"Mobilier d'occasion"
    • addedInput schema / properties / purchase_date / description
      Added value: +"Date d'achat au format Y-m-d"
    • addedInput schema / properties / tva_rate / description
      Added value: +"Taux de TVA en pourcentage (ex: 20 pour 20%)"
  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?

Beyond the supplied idempotentHint/destructiveHint, the description discloses a real side effect: annual depreciation is automatically recalculated when amount or duration_years changes, and unlisted fields are left untouched. It also pins the currency (euros), which the annotations cannot convey. It stops short of saying whether the recalculation overwrites prior depreciation entries, which is the main residual ambiguity for a destructiveHint tool.

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 the partial-update rule before the unit note and side effect. Nothing is wasted, though the euro statement is close to restating 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 an 8-parameter update tool with no output schema, the description covers the essential unknowns: partial-update semantics, currency, and the automatic depreciation recalculation. Only failure behavior for an invalid furniture_id and the shape of the returned/updated record are unaddressed, which are minor gaps.

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 the schema already explains every parameter including units and formats. The description only adds that the amount is in euros (partially redundant with "Montant TTC en euros") and that amount/duration_years drive depreciation recalculation, which is genuinely new but narrow. Baseline 3 is appropriate.

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 states a specific verb and resource ("Met à jour un élément de mobilier existant"), which is immediately distinguishable from create_furniture, delete_furniture and list_furniture by the verb alone. It does not explicitly name a sibling or a boundary case, but the operation is unambiguous.

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?

"Seuls les champs fournis sont modifiés (mise à jour partielle)" tells the agent how to call it (PATCH-style, send only changed fields), which is useful implied guidance. However, there is no when-to-use vs. when-not guidance, no prerequisites (e.g. existence of the furniture_id), and no pointer to an alternative such as create_furniture or compute_depreciation.

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