boondmanager-mcp-server

Modifier un(e) facture

boond_invoices_update

Idempotent

Modify specific fields of an existing invoice by ID with partial updates. Provide only the fields to change; array fields are replaced, and payment dates can be set alongside status changes.

Instructions

Met à jour un(e) facture existant(e), identifié(e) par son ID.

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_invoices_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 facture à modifier
`note`	No	Notes
`state`	No	État de la facture : ID de `boond://dictionary/states/invoices` (ex: 0 = Création, 1 = Transmis au client)
`taxRate`	No	Taux de TVA (%)
`reference`	No	Référence de la facture
`invoiceDate`	No	Date de facturation (YYYY-MM-DD)
`paymentMethod`	No	Mode de règlement : ID de `boond://dictionary/paymentMethods`
`invoiceRecords`	No	Lignes de facture Boond
`invoicePayments`	No	Paiements client de la facture
`amountExcludingTax`	No	Montant HT
`expectedPaymentDate`	No	Date d'échéance (YYYY-MM-DD) — pas la date de règlement, voir `performedPaymentDate`
`performedPaymentDate`	No	Date de règlement effectif (YYYY-MM-DD, `""` pour l'effacer). À envoyer dans le même appel que le passage de `state` à l'état « payée » : sans elle, BoondManager date le règlement du jour du changement d'état. Si la date est encore écrasée, rappeler `boond_invoices_update` avec ce seul champ.

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.

Changed3 schema fields changedv2.18.0Oct 2, 2026

changedInput schema / properties / expectedPaymentDate / description

Previous value: -"Date d'échéance/paiement attendu (YYYY-MM-DD)"New value: +"Date d'échéance (YYYY-MM-DD) — pas la date de règlement, voir `performedPaymentDate`"

addedInput schema / properties / paymentMethod

Added value: +{
+  "description": "Mode de règlement : ID de `boond://dictionary/paymentMethods`",
+  "maximum": 9007199254740991,
+  "minimum": -1,
+  "type": "integer"
+}

addedInput schema / properties / performedPaymentDate

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    {
+      "const": "",
+      "type": "string"
+    }
+  ],
+  "description": "Date de règlement effectif (YYYY-MM-DD, `\"\"` pour l'effacer). À envoyer dans le même appel que le passage de `state` à l'état « payée » : sans elle, BoondManager date le règlement du jour du changement d'état. Si la date est encore écrasée, rappeler `boond_invoices_update` avec ce seul champ."
+}

Changed3 schema fields changedv2.17.0Sep 26, 2026

removedInput schema / properties / id / minLength
```
Removed value: -1
```
addedInput schema / properties / id / pattern
```
Added value: +"^\\d+$"
```

changedInput schema / properties / state / description

Previous value: -"État de la facture"New value: +"État de la facture : ID de `boond://dictionary/states/invoices` (ex: 0 = Création, 1 = Transmis au client)"

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#"

Changed4 schema fields changedv2.8.0Jun 29, 2026

removedInput schema / properties / dueDate

Removed value: -{
-  "description": "Date d'échéance (YYYY-MM-DD)",
-  "type": "string"
-}

addedInput schema / properties / expectedPaymentDate

Added value: +{
+  "description": "Date d'échéance/paiement attendu (YYYY-MM-DD)",
+  "type": "string"
+}

addedInput schema / properties / invoicePayments

Added value: +{
+  "description": "Paiements client de la facture",
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / invoiceRecords

Added value: +{
+  "description": "Lignes de facture Boond",
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

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?

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses that updates are partial (only supplied fields are written), that array fields are replaced rather than merged, and that boond_rights_get can pre-check permission to avoid a 403. These are exactly the mutation semantics an agent needs and they are not inferable from the annotations.

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?

Front-loaded purpose, then when/alternative, then three compact bullets on behavior. Every sentence carries information; no filler or restatement of the title.

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?

For a 12-parameter mutation tool the description covers the risky behaviors (partial write, array replacement, rights pre-check) and briefly notes the return ('confirmation et fiche mise à jour'), with the output schema carrying the rest. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuine cross-field behavior: partial-write semantics and the array replace-not-merge rule, which no single parameter description communicates. It does not add per-field detail beyond the schema, hence not a 5.

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?

States a specific verb and resource ('Met à jour un(e) facture existant(e)'), makes the identifier explicit ('identifié(e) par son ID'), and names the sibling it differs from (boond_invoices_create). An agent can distinguish it from boond_invoices_get/search/create without opening a schema.

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?

Explicit 'Quand' clause scopes use to modifying fields of an existing record, and the 'Plutôt que' clause routes to boond_invoices_create when the record does not yet exist. Both the when and the alternative are named outright.

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

Deploy Server