Skip to main content
Glama
OpenLMNP

OpenLMNP

List Property Components

list_property_components
Read-only

Retrieve a property's depreciation components by ventilation, with each component's percentage, calculation base, duration, and annual depreciation; percentages must total 100%.

Instructions

Liste les composants d'amortissement par ventilation d'un bien immobilier (gros œuvre, toiture, électricité, etc.). Retourne chaque composant avec son pourcentage, la base de calcul, la durée et l'amortissement annuel. La somme des pourcentages doit être 100 %.

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

Input Schema

NameRequiredDescriptionDefault
property_idYesIdentifiant du bien immobilier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / property_id / description
      Added value: +"Identifiant du bien immobilier"
  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?

readOnlyHint=true already tells the agent this is a safe read, but the description adds real value beyond that: it enumerates the returned fields per component (pourcentage, base de calcul, durée, amortissement annuel) and states a data invariant (percentages must sum to 100%). It does not say what happens when a property has no components allocated, which is the main remaining gap.

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?

Three short sentences, each doing a distinct job: what is listed, what is returned, and the invariant to expect. Purpose is front-loaded and there is no filler or repetition of the tool name.

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?

With one well-documented parameter, a read-only annotation, and no output schema, the description compensates well by describing the shape of the returned components. A brief note on empty/unallocated cases and on how it relates to the depreciation-computation siblings would make it fully self-sufficient.

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?

There is one parameter with 100% schema description coverage ('Identifiant du bien immobilier'), so the schema already carries the semantics. The phrase 'd'un bien immobilier' in the description restates it without adding format, validation, or sourcing details, which is the expected baseline 3 when the schema does the work.

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 ('Liste') and a precise resource ('composants d'amortissement par ventilation d'un bien immobilier'), with concrete examples (gros œuvre, toiture, électricité) that make the domain unambiguous. It does not name a sibling to differentiate from (e.g. list_property_works, compute_depreciation), but the resource is distinct enough that an agent can separate it from generic work-listing tools.

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: the agent infers it should call this to inspect how a property's value is split into depreciable components. There is no explicit when-to-use, no prerequisites (e.g. whether the property must already have components defined), and no routing advice versus compute_depreciation or list_property_works.

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