Skip to main content
Glama
OpenLMNP

OpenLMNP

Create Furniture

create_furniture
Destructive

Record a depreciable furniture item for an LMNP rental property to track its purchase cost and automatically compute annual depreciation over 5 years (3 years for second-hand items).

Instructions

Crée un élément de mobilier amortissable pour un bien LMNP. Le montant est en euros. La durée d'amortissement est de 5 ans par défaut (3 ans pour le mobilier d'occasion). L'amortissement annuel est calculé automatiquement.

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>",
      "description": "<description>",
      "amount": "<amount>",
      "purchase_date": "<purchase_date>"
    },
    "name": "create_furniture"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesMontant TTC en euros (ex: 850.00)
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%, 0 pour exonéré)
descriptionYesDescription du mobilier (ex: Canapé convertible, Lave-vaisselle)
property_idYesIdentifiant du bien immobilier
is_dedicatedNoMobilier 100% dédié à la location (true) ou au prorata de la quote-part (false, défaut)
purchase_dateYesDate d'achat au format Y-m-d (ex: 2025-03-15)
duration_yearsNoDurée d'amortissement en années (défaut : 5 ans neuf, 3 ans occasion)
is_second_handNoMobilier d'occasion (true) — durée réduite à 3 ans par défaut

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 (ex: 850.00)"
    • addedInput schema / properties / description / description
      Added value: +"Description du mobilier (ex: Canapé convertible, Lave-vaisselle)"
    • addedInput schema / properties / duration_years / description
      Added value: +"Durée d'amortissement en années (défaut : 5 ans neuf, 3 ans occasion)"
    • addedInput schema / properties / is_dedicated / description
      Added value: +"Mobilier 100% dédié à la location (true) ou au prorata de la quote-part (false, défaut)"
    • addedInput schema / properties / is_second_hand / description
      Added value: +"Mobilier d'occasion (true) — durée réduite à 3 ans par défaut"
    • addedInput schema / properties / property_id / description
      Added value: +"Identifiant du bien immobilier"
    • addedInput schema / properties / purchase_date / description
      Added value: +"Date d'achat au format Y-m-d (ex: 2025-03-15)"
    • addedInput schema / properties / tva_rate / description
      Added value: +"Taux de TVA en pourcentage (ex: 20 pour 20%, 0 pour exonéré)"
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations supply only destructiveHint=true, so the description carries most of the burden and does add real behavior: the 5-year default schedule, the 3-year second-hand reduction, and the fact that annual depreciation is computed automatically. It does not disclose what is returned, whether the record can be edited afterwards, or why a create operation is flagged destructive.

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 scope, with no filler. The 'montant en euros' sentence mildly duplicates the schema's amount description but still serves as a quick sanity check for an agent skimming the text.

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 an 8-parameter creation tool with no output schema and only a destructive hint for annotations, the definition covers the depreciation domain logic well. It leaves unaddressed what a successful call returns (e.g., the new item's identifier) and whether the auto-computed depreciation can be overridden by duration_years.

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 amount, tva_rate, is_second_hand, duration_years and the rest. The description only reinforces two of these (euro currency and the duration defaults), adding nothing the schema does not already state; 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?

States a specific verb and resource – creating a depreciable furniture item attached to an LMNP property – which is clearly distinguishable from the surrounding expense/income/property creation siblings. It stops short of naming or contrasting any alternative tool, but the resource itself 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?

The LMNP/amortizable framing implies when the tool applies, and the description signals that depreciation is handled for you rather than via a separate compute call. However, it never states when to use this instead of create_expense for a furniture purchase, nor any prerequisites such as the property already existing.

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