boondmanager-mcp-server

Modifier un(e) note de frais

boond_expenses_update

Idempotent

Update an existing expense report by ID with partial field updates. Check user rights via boond_rights_get before modifying to avoid 403 errors, then receive confirmation and the updated report.

Instructions

Met à jour un(e) note de frais existant(e), identifié(e) par son ID.

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_expenses_create si l'enregistrement n'existe pas encore.

Mise à jour partielle : seuls les champs fournis sont écrits, les autres sont laissés en place.
Attention aux champs de type tableau, qui sont remplacés et non fusionnés.
boond_rights_get dit si l'utilisateur a ce droit sur l'enregistrement avant d'essayer (un 403 évité).

Returns : confirmation et fiche mise à jour.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	ID de la note de frais à modifier
`closed`	No	Clôturer la note de frais
`advance`	No	Avance à reprendre
`actualExpenses`	No	⚠️ REMPLACE l'intégralité des lignes existantes. Pour ajouter une ligne, relire la note via `boond_expenses_get` et renvoyer l'ensemble des lignes. Omettre pour ne toucher qu'aux autres champs.
`currencyAgency`	No	ID de devise de l'agence
`exchangeRateAgency`	No	Taux de change agence
`informationComments`	No	Commentaires
`ratePerKilometerTypeReference`	No	Code du barème kilométrique

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Identifiant de l'entité créée/modifiée
`type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2.17.0Sep 26, 2026
- addedInput schema / properties / actualExpenses / items / properties / batchId / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / actualExpenses / items / properties / deliveryId / minLength
```
Removed value: -1
```
- addedInput schema / properties / actualExpenses / items / properties / deliveryId / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / actualExpenses / items / properties / projectId / minLength
```
Removed value: -1
```
- addedInput schema / properties / actualExpenses / items / properties / projectId / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / id / minLength
```
Removed value: -1
```
- addedInput schema / properties / id / pattern
```
Added value: +"^\\d+$"
```

Changed10 schema fields changedv2.14.0Aug 22, 2026

addedInput schema / properties / actualExpenses

Added value: +{
+  "description": "⚠️ REMPLACE l'intégralité des lignes existantes. Pour ajouter une ligne, relire la note via `boond_expenses_get` et renvoyer l'ensemble des lignes. Omettre pour ne toucher qu'aux autres champs.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "activityType": {
+        "default": "production",
+        "description": "Type d'activité rattachée au frais.",
+        "enum": [
+          "production",
+          "internal",
+          "absence"
+        ],
+        "type": "string"
+      },
+      "amountIncludingTax": {
+        "description": "Montant TTC. Ignoré pour un frais kilométrique (recalculé = km × barème).",
+        "type": "number"
+      },
+      "batchId": {
+        "description": "ID du lot. Absent = aucun lot.",
+        "type": "string"
+      },
+      "currency": {
+        "default": 0,
+        "description": "ID de devise (`setting.currency`, 0 = EUR).",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "deliveryId": {
+        "description": "ID de la prestation (delivery) à imputer. Obligatoire — voir `boond_expenses_default`.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "exchangeRate": {
+        "default": 1,
+        "description": "Taux de change vers la devise agence.",
+        "type": "number"
+      },
+      "expenseTypeReference": {
+        "description": "Code du type de frais (`reference`), à lire via `boond_expenses_default` — les types de frais sont définis par agence et ne figurent PAS dans `boond_application_dictionary`. À omettre pour un frais kilométrique.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "file": {
+        "description": "ID du justificatif déjà téléversé, suffixé (ex: `52979_proof`). Un fichier doit d'abord être créé via `boond_documents_create` (`parentType: 'expensesReport'`).",
+        "type": "string"
+      },
+      "isKilometricExpense": {
+        "default": false,
+        "description": "`true` pour un frais kilométrique : renseigner `numberOfKilometers` et omettre `expenseTypeReference`.",
+        "type": "boolean"
+      },
+      "numberOfKilometers": {
+        "description": "Nombre de kilomètres (frais kilométrique uniquement).",
+        "type": "number"
+      },
+      "projectId": {
+        "description": "ID du projet à imputer. Obligatoire — les couples (projet, prestation) autorisés sont donnés par `boond_expenses_default`.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "reinvoiced": {
+        "default": false,
+        "description": "Frais refacturable au client.",
+        "type": "boolean"
+      },
+      "startDate": {
+        "description": "Date du frais (YYYY-MM-DD). Doit tomber dans le mois `term` de la note de frais.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "tax": {
+        "description": "Taux de TVA en % (ex: 20 pour 20 %) — un taux, pas un montant. Défaut API: 0.",
+        "type": "number"
+      },
+      "title": {
+        "description": "Description libre de la ligne (marchand, motif, invités...).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "startDate",
+      "projectId",
+      "deliveryId"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / advance

Added value: +{
+  "description": "Avance à reprendre",
+  "type": "number"
+}

removedInput schema / properties / amount

Removed value: -{
-  "description": "Montant",
-  "type": "number"
-}

addedInput schema / properties / closed

Added value: +{
+  "description": "Clôturer la note de frais",
+  "type": "boolean"
+}

addedInput schema / properties / currencyAgency

Added value: +{
+  "description": "ID de devise de l'agence",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / informationComments

Added value: +{
+  "description": "Commentaires",
+  "type": "string"
+}

removedInput schema / properties / note

Removed value: -{
-  "description": "Description",
-  "type": "string"
-}

addedInput schema / properties / ratePerKilometerTypeReference

Added value: +{
+  "description": "Code du barème kilométrique",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedInput schema / properties / state

Removed value: -{
-  "description": "État",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

removedInput schema / properties / term

Removed value: -{
-  "description": "Période de la note de frais (YYYY-MM)",
-  "type": "string"
-}

Changed2 schema fields changedv2.12.2Aug 14, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedv2.8.0Jun 29, 2026

addedInput schema / properties / exchangeRateAgency

Added value: +{
+  "description": "Taux de change agence",
+  "type": "number"
+}

addedInput schema / properties / term

Added value: +{
+  "description": "Période de la note de frais (YYYY-MM)",
+  "type": "string"
+}

Changed1 schema field changedv2.7.0Jun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Identifiant de l'entité créée/modifiée",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses partial update semantics ('seuls les champs fournis sont écrits'), warns that array fields are replaced not merged, and explains the behavior of `actualExpenses` replacement with a specific read-then-resend strategy. It also mentions the return value ('confirmation et fiche mise à jour'). Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) are consistent with the description, and the description adds meaningful behavioral context beyond those hints.

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?

The description is compact and well-structured: a one-sentence definition, a 'Quand' section, a 'Plutôt que' section, bullet points for key behaviors, and a return note. Every sentence earns its place, and the most important usage guidance is front-loaded.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, nested array objects, partial update semantics), the description covers the essential operational knowledge: when to use, what to avoid, how to handle array replacement, how to check rights, and what the response contains. The output schema exists, so return values don't need further explanation. The description is complete for an agent to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by highlighting the critical `actualExpenses` replacement behavior and the workflow for adding a line (read via `boond_expenses_get` and resend all lines). It also references `boond_expenses_default` for valid project/delivery pairs, which is useful context not in the schema. However, most parameter-level semantics are already in the schema, so the description's added value is focused on a few key parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Met à jour'), a specific resource ('note de frais existant(e)'), and the identifier used ('par son ID'). It clearly distinguishes this from the create sibling by naming `boond_expenses_create` as the alternative when the record doesn't exist yet. The title also aligns with the description, and the tool name is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly says when to use this tool: 'pour modifier quelques champs d'un enregistrement déjà en base.' It also gives a clear exclusion: use `boond_expenses_create` if the record doesn't exist yet. It even provides a pre-check recommendation via `boond_rights_get` to avoid a 403, which is actionable usage guidance.

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

Deploy Server