Skip to main content
Glama
OpenLMNP

OpenLMNP

Create Income

create_income
Destructive

Adds a rental income entry for a furnished LMNP property, including amount, date, and booking source for accurate tax tracking.

Instructions

Crée un revenu locatif pour un bien LMNP. Le montant est en euros (ex: 125.50). La source peut être : airbnb, booking, abritel, direct, other.

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>",
      "income_date": "<income_date>",
      "amount": "<amount>",
      "source": "<source>"
    },
    "name": "create_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoNotes libres
amountYesMontant TTC en euros (ex: 125.50)
sourceYesPlateforme source : airbnb, booking, abritel, direct, other
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%, 0 pour exonéré)
guest_nameNoNom du voyageur
income_dateYesDate du revenu au format Y-m-d (ex: 2025-03-15)
property_idYesIdentifiant du bien immobilier
tourist_taxNoTaxe de séjour en euros (ex: 2.50)
checkin_dateNoDate d'arrivée au format Y-m-d
platform_feeNoCommission plateforme en euros
checkout_dateNoDate de départ au format Y-m-d
reservation_refNoRéférence de réservation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.0.1
    • addedInput schema / properties / amount / description
      Added value: +"Montant TTC en euros (ex: 125.50)"
    • addedInput schema / properties / checkin_date / description
      Added value: +"Date d'arrivée au format Y-m-d"
    • addedInput schema / properties / checkout_date / description
      Added value: +"Date de départ au format Y-m-d"
    • addedInput schema / properties / guest_name / description
      Added value: +"Nom du voyageur"
    • addedInput schema / properties / income_date / description
      Added value: +"Date du revenu au format Y-m-d (ex: 2025-03-15)"
    • addedInput schema / properties / notes / description
      Added value: +"Notes libres"
    • addedInput schema / properties / platform_fee / description
      Added value: +"Commission plateforme en euros"
    • addedInput schema / properties / property_id / description
      Added value: +"Identifiant du bien immobilier"
    • addedInput schema / properties / reservation_ref / description
      Added value: +"Référence de réservation"
    • addedInput schema / properties / source / description
      Added value: +"Plateforme source : airbnb, booking, abritel, direct, other"
    • addedInput schema / properties / tourist_tax / description
      Added value: +"Taxe de séjour en euros (ex: 2.50)"
    • addedInput schema / properties / tva_rate / description
      Added value: +"Taux de TVA en pourcentage (ex: 20 pour 20%, 0 pour exonéré)"
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

The only annotation is destructiveHint=true, so the description carries the burden of explaining the write's consequences, and it does not: nothing about duplicate handling, whether the entry feeds TVA/depreciation/fiscal computations, permission needs, or irreversibility. It does contribute the currency convention (euros, ex: 125.50) and the source vocabulary, which is real but modest added context for a mutation.

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?

Three short sentences with the purpose front-loaded and no filler. Slight redundancy in repeating the amount example and source list that the schema already contains, but it is well within an efficient length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter mutation with no output schema, the description covers what is being created and the currency/source conventions, and the schema fully documents the remaining fields. It omits the consequences of creation (fiscal impact, duplicate behavior) and which optional fields matter in practice, leaving a meaningful 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%, so every one of the 12 parameters is already documented in the schema, and the description's two parameter statements (amount in euros, allowed source values) largely restate it. Baseline 3 applies; no new semantics such as how tva_rate interacts with amount or when tourist_tax should be populated.

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?

"Crée un revenu locatif pour un bien LMNP" gives a specific verb (crée) and resource (revenu locatif) plus the domain scope (LMNP rental property), which clearly separates it from create_expense or create_furniture. It stops short of naming a sibling alternative, so it is clear but not fully differentiated.

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 LMNP framing and the enumerated sources (airbnb, booking, abritel, direct, other) suggest the recording scenario, but there is no explicit when-to-use, no when-not, and no mention of update_income for correcting an existing entry. An agent must infer the boundary from the tool name alone.

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