Skip to main content
Glama
OpenLMNP

OpenLMNP

List Property Works

list_property_works
Read-only

Retrieve depreciable real estate works with an optional property filter and return descriptions, amounts, dates, depreciation durations, annual depreciation, and dedicated flags.

Instructions

Liste les travaux immobiliers amortissables de l'utilisateur avec filtre optionnel par bien. Retourne pour chaque travail : description, montant TTC/HT, date, durée d'amortissement, amortissement annuel et flag dédié.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_property_works"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idNoFiltrer par identifiant de bien (optionnel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / property_id / description
      Added value: +"Filtrer par identifiant de bien (optionnel)"
  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?

Annotations only declare readOnlyHint=true, so the description must add the rest, and it does: it scopes results to the current user and lists the concrete fields returned per work (description, TTC/HT amount, date, depreciation duration, annual depreciation, dedicated flag). It omits ordering and pagination behavior, keeping 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.

Conciseness4/5

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

Two tight sentences, with the operation and scope front-loaded and the return fields following. No filler, though the return-field list is dense enough that it borders on being a single long clause.

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 one-optional-parameter read-only tool with no output schema, the description covers scope, filtering, and the shape of returned items, which compensates for the missing output schema. It lacks any indication of result volume or ordering, a minor residual gap.

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% and the single property_id parameter is already documented as the optional property filter. The description's phrase "filtre optionnel par bien" merely restates the schema, adding no format or edge-case detail, 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?

States a specific verb ("Liste") and a precise resource ("travaux immobiliers amortissables de l'utilisateur"), and even enumerates what is returned per work item. It does not distinguish itself from nearby siblings like list_property_components or get_property, so it stops short of a 5.

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?

Mentions that filtering by property is optional, which implies the two usage modes (all works vs. one property's works). There is no explicit guidance on when to prefer this tool over list_property_components, get_property, or the compute_depreciation sibling, so usage is only implied.

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