boondmanager-mcp-server

Modifier un(e) facture

boond_invoices_update

Idempotent

Update an existing invoice by ID, modifying only the fields you provide. Ideal for changing specific details like state, date, or payment info without recreating the record.

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.

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
`taxRate`	No	Taux de TVA (%)
`reference`	No	Référence de la facture
`invoiceDate`	No	Date de facturation (YYYY-MM-DD)
`invoiceRecords`	No	Lignes de facture Boond
`invoicePayments`	No	Paiements client de la facture
`amountExcludingTax`	No	Montant HT
`expectedPaymentDate`	No	Date d'échéance/paiement attendu (YYYY-MM-DD)

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.

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.7/5.0

Behavior4/5

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

Annotations already cover read-only, destructive, and idempotent hints. The description adds valuable behavioral context beyond those: partial update semantics, the warning that array fields are replaced rather than merged, and the return payload. This is strong supplementary disclosure for an update operation.

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 front-loaded with the core action, followed by a compact 'Quand / Plutôt que' usage block and two focused bullet points. Every sentence earns its place; there is no filler or repetition.

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 output schema exists, the description does not need to document return structure in depth. It covers purpose, usage boundaries, partial-update behavior, array-replacement risks, and the return confirmation, making it complete enough for an agent to select and invoke the 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 baseline is 3. The description goes further by clarifying that only provided fields are written and that array parameters like invoiceRecords and invoicePayments are replaced, not merged. This adds meaningful semantics that the schema alone does not convey.

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 opens with a specific verb and resource: 'Met à jour un(e) facture existant(e), identifié(e) par son ID.' This clearly distinguishes the tool as an update operation for existing invoices, and the explicit contrast with boond_invoices_create helps an agent identify it among the many CRUD siblings.

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 states both when to use this tool ('pour modifier quelques champs d'un enregistrement déjà en base') and when not to, explicitly routing the agent to boond_invoices_create if the record does not yet exist. This is direct, unambiguous 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