Skip to main content
Glama
OpenLMNP

OpenLMNP

Create Property Work

create_property_work
Destructive

Create a depreciable work item for an LMNP property with euro amount and work date. Annual depreciation is calculated automatically over 10 years, including quote-part for shared costs.

Instructions

Crée un poste de travaux immobiliers amortissables pour un bien LMNP. Le montant est en euros. La durée d'amortissement est de 10 ans par défaut. L'amortissement annuel est calculé automatiquement en tenant compte de la quote-part si le poste n'est pas dédié.

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>",
      "work_date": "<work_date>"
    },
    "name": "create_property_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesMontant TTC en euros (ex: 12500.00)
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%, 10 pour taux réduit travaux, 0 pour exonéré)
work_dateYesDate des travaux au format Y-m-d (ex: 2025-06-01)
descriptionYesDescription des travaux (ex: Réfection de la salle de bain, Installation cuisine)
property_idYesIdentifiant du bien immobilier
is_dedicatedNoTravaux 100% dédiés à la location (true) ou au prorata de la quote-part (false, défaut)
duration_yearsNoDurée d'amortissement en années (défaut : 10 ans)

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 (ex: 12500.00)"
    • addedInput schema / properties / description / description
      Added value: +"Description des travaux (ex: Réfection de la salle de bain, Installation cuisine)"
    • addedInput schema / properties / duration_years / description
      Added value: +"Durée d'amortissement en années (défaut : 10 ans)"
    • addedInput schema / properties / is_dedicated / description
      Added value: +"Travaux 100% dédiés à la location (true) ou au prorata de la quote-part (false, défaut)"
    • addedInput schema / properties / property_id / description
      Added value: +"Identifiant du bien immobilier"
    • addedInput schema / properties / tva_rate / description
      Added value: +"Taux de TVA en pourcentage (ex: 20 pour 20%, 10 pour taux réduit travaux, 0 pour exonéré)"
    • addedInput schema / properties / work_date / description
      Added value: +"Date des travaux au format Y-m-d (ex: 2025-06-01)"
  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?

The only annotation is destructiveHint=true, which conveys almost nothing useful for a creation tool. The description compensates by disclosing real business behavior: a 10-year default duration and automatic annual depreciation that applies the quote-part when the item is not dedicated. It does not describe side effects on the depreciation schedule or what is returned, which keeps it short of a 5.

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 resource, and each one carries information. The sentence 'Le montant est en euros' is slightly redundant with the schema's 'Montant TTC en euros', a minor overlap.

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 7-parameter mutation with no output schema and only a destructiveHint annotation, the description covers defaults and the depreciation rule well. It remains silent on the return value, on whether the created item appears in list_property_works/compute_depreciation, and on any validation or permission requirements.

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 adds meaning beyond the schema by explaining the consequence of is_dedicated=false (annual depreciation prorated by the quote-part) and by confirming the amount basis and default duration. This is genuine semantic value rather than restatement.

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: creating an amortizable real-estate work item ('poste de travaux immobiliers amortissables') attached to an LMNP property. The resource is clearly distinct from siblings like create_expense or create_furniture, though no sibling is named explicitly.

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?

Usage is only implied by the domain wording (LMNP, amortizable work item); there is no explicit statement of when to choose this over create_expense or create_furniture, nor any precondition such as the property having to exist. An agent can infer the context but must reason about the alternative.

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