Skip to main content
Glama
OpenLMNP

OpenLMNP

List Furniture

list_furniture
Read-only

Retrieve a user's furniture and depreciable equipment, optionally filtered by property, to review purchase amounts, dates, depreciation periods, annual depreciation, and dedicated/used flags.

Instructions

Liste le mobilier et équipements amortissables de l'utilisateur avec filtre optionnel par bien. Retourne pour chaque élément : description, montant d'achat, date, durée d'amortissement, amortissement annuel, flag dédié et occasion.

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_furniture"
  }
}

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 already declare readOnlyHint=true, so safety is covered; the description adds valuable content by enumerating exactly what is returned for each item (description, purchase amount, date, amortization duration, annual amortization, dedicated flag, second-hand flag). It does not mention pagination, sorting, or volume limits, 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.

Conciseness4/5

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

Two sentences: scope first, then the per-item return fields. Every clause earns its place and nothing is padded, though the return-field list is a long enumeration that could be tightened.

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 no output schema, the description carries the burden of describing return values and does so field by field, which is the right call for a list tool. Combined with readOnlyHint covering safety and a fully documented parameter, an agent has enough to call it correctly; only ordering and result-size behavior are 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 description coverage is 100% and the single parameter already documents itself as an optional property id filter. The description only restates that the filter is optional and by property, adding no syntax or semantics beyond the schema, 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 and resource ('Liste le mobilier et équipements amortissables de l'utilisateur') and narrows scope to depreciable items owned by the user. It is clearly distinguishable from the create/update/delete_furniture siblings by the listing verb, though it never names those siblings to reinforce the contrast.

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 optional property filter implies use ('filtre optionnel par bien'), so an agent can infer it should be used to enumerate furniture, optionally scoped to one property. There is no explicit when-to-use or when-not-to-use guidance and no reference to sibling tools such as list_properties or compute_depreciation.

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