Skip to main content
Glama
OpenLMNP

OpenLMNP

Update Income

update_income
Destructive

Update an existing rental income record by changing only the fields you provide, such as amount, dates, guest details, platform fees, or notes.

Instructions

Met à jour un revenu locatif existant. Seuls les champs fournis sont modifiés (mise à jour partielle). Le montant est en euros.

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": {
      "income_id": "<income_id>"
    },
    "name": "update_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoNotes libres
amountNoMontant TTC en euros
sourceNoPlateforme source : airbnb, booking, abritel, direct, other
tva_rateNoTaux de TVA en pourcentage (ex: 20 pour 20%)
income_idYesIdentifiant du revenu à mettre à jour
guest_nameNoNom du voyageur
income_dateNoDate du revenu au format Y-m-d
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"
    • 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"
    • addedInput schema / properties / income_id / description
      Added value: +"Identifiant du revenu à mettre à jour"
    • addedInput schema / properties / notes / description
      Added value: +"Notes libres"
    • addedInput schema / properties / platform_fee / description
      Added value: +"Commission plateforme en euros"
    • 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%)"
  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?

With destructiveHint=true already supplied, the description still adds a substantive behavioral fact: only the fields provided are written, so omitted fields are left untouched rather than nulled. That is exactly the detail an agent needs before calling a 12-parameter mutation. It does not cover permissions, reversibility, or behavior when income_id is unknown, hence not 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.

Conciseness5/5

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

Three short sentences, no filler: the action first, the partial-update rule second, the currency note last. Every sentence carries information an agent cannot get from the name alone.

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?

The schema is fully self-documenting and there is no output schema to explain, so the core is covered. However, for a mutation flagged destructiveHint=true the description says nothing about whether an update can overwrite data destructively, whether it requires authorization, or what happens when income_id does not match a record.

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% — every one of the 12 properties carries a French description including formats (Y-m-d) and the TVA example. The description's 'Le montant est en euros' merely restates the schema's 'Montant TTC en euros', so nothing is added beyond the schema; 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?

The description states a specific verb and resource ('Met à jour un revenu locatif existant'), which cleanly separates it from create_income, delete_income, and get_income by specifying that the record must already exist. It does not explicitly name a sibling or a boundary case, 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?

Usage is only implied: 'existant' tells the agent this is for records already present, and 'mise à jour partielle' hints that a full payload is unnecessary. There is no explicit when-to-use versus create_income/update_expense guidance and no stated prerequisites, so it is minimum viable.

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