Skip to main content
Glama
OpenLMNP

OpenLMNP

Compute Depreciation

compute_depreciation
Read-only

Calculates annual LMNP depreciation for a property and tax year, returning euro amounts by building, works, and furniture components plus the yearly total.

Instructions

Calcule le détail des amortissements LMNP pour un bien immobilier et une année donnée. Retourne la ventilation par composant immeuble, travaux et mobilier, ainsi que le total annuel, tous les montants exprimés en euros.

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>",
      "year": "<year>"
    },
    "name": "compute_depreciation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesAnnée fiscale (ex : 2025)
property_idYesIdentifiant du bien immobilier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / property_id / description
      Added value: +"Identifiant du bien immobilier"
    • addedInput schema / properties / year / description
      Added value: +"Année fiscale (ex : 2025)"
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: the return is a breakdown by component (immeuble, travaux, mobilier) plus an annual total, and all amounts are in euros. It does not say what happens with missing data or whether the result depends on previously stored components, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both of which earn their place: the first states the computation and its scope, the second states the return structure and currency. The purpose is front-loaded with no filler.

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 two-parameter read-only computation with no output schema, the description does the important extra work of explaining what the response contains and in which currency. It is nearly complete; only the data dependencies (whether components must exist beforehand) are left unstated.

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 coverage is 100% and both parameters (property_id, year with the example 2025) are documented in the schema. The description only restates the two inputs at a high level ('un bien immobilier et une année donnée'), adding no format, range, or constraint details, so the baseline 3 applies.

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 gives a specific verb and resource: it computes LMNP depreciation detail for a property and a given year, which clearly separates it from siblings like compute_tva, compute_loan_schedule, or compute_fiscal_year. It never names an alternative explicitly, but the LMNP-depreciation domain is distinctive enough that an agent can route to it.

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 phrase 'pour un bien immobilier et une année donnée'; there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as compute_fiscal_year for the broader tax computation. An agent can infer the context but receives no exclusions or prerequisites (e.g. whether furniture/works must already be recorded).

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