Skip to main content
Glama
OpenLMNP

OpenLMNP

Get Property

get_property
Read-only

Retrieve complete details for one property—characteristics, financial amounts, depreciable base, and counts of components, works, furniture, and loans—to review its LMNP accounting record.

Instructions

Retourne le détail complet d'un bien immobilier : caractéristiques, montants financiers, base amortissable, et comptage des composants, travaux, mobilier et emprunts associés.

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": "get_property"
  }
}

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

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a non-mutating read, so the annotation supplies the safety profile. The description adds genuine value by disclosing the scope of what comes back (characteristics, financial amounts, amortizable base, aggregated counts), but says nothing about behavior on a missing/invalid property_id, permissions, or the shape of the response. That is adequate but not rich.

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?

A single sentence that front-loads the action and then lists the returned content, with no filler. The enumeration of counts is long but each item carries informational weight.

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?

There is no output schema, so the description's enumeration of returned fields is the only signal an agent gets about the payload, and it does that reasonably well for a one-parameter read tool. It stops short of describing the response structure (nesting of the financial data versus the counts).

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% with a single integer property_id that the schema already documents, so the description need only match that baseline. It adds no syntax, format, or sourcing guidance for the identifier beyond what the schema provides.

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 uses a specific verb-and-resource pairing ('Retourne le détail complet d'un bien immobilier') and enumerates the content returned (characteristics, financial amounts, amortizable base, counts of components/works/furniture/loans), which partly separates it from siblings such as get_expense or get_loan. It does not explicitly name or contrast itself with any alternative, so it falls 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing states when to call this tool rather than the sibling listers (list_property_components, list_property_works) or update_property. The only guidance is implicit: fetch a property's full detail by id. There are no prerequisites, exclusions, or alternative-selection cues.

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