boondmanager-mcp-server

Créer un(e) facture

boond_invoices_create

Create a new invoice in BoondManager when no matching record exists; use update to modify existing invoices, and search first to avoid duplicates.

Instructions

Crée un(e) facture dans BoondManager.

Quand : pour ajouter un(e) facture inexistant(e). Plutôt que : boond_invoices_update pour modifier un enregistrement existant, et boond_invoices_search d'abord pour vérifier qu'il n'existe pas déjà.

Écriture réelle et non idempotente : deux appels identiques créent deux enregistrements (l'API ne déduplique pas).
Les ID de relations et les états/types sont des ID numériques BoondManager, à résoudre au préalable (recherches d'entités, boond://dictionary/*).

Returns : confirmation, ID créé, et la fiche complète. structuredContent.id est réutilisable directement pour chaîner un appel.

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No	Notes / commentaires
`state`	No	État de la facture : ID de `boond://dictionary/states/invoices` (ex: 0 = Création, 1 = Transmis au client)
`orderId`	No	ID du bon de commande associé
`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."
+}

Changed2 schema fields changedv2.17.0Sep 26, 2026

addedInput schema / properties / orderId / 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#"

Changed7 schema fields changedv2.8.0Jun 29, 2026

removedInput schema / properties / companyId

Removed value: -{
-  "description": "ID de la société facturée",
-  "type": "string"
-}

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"
+}

addedInput schema / properties / orderId

Added value: +{
+  "description": "ID du bon de commande associé",
+  "type": "string"
+}

removedInput schema / properties / projectId

Removed value: -{
-  "description": "ID du projet associé",
-  "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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false. The description adds valuable behavior beyond them: the concrete non-idempotence consequence ('deux appels identiques créent deux enregistrements'), the need to resolve relation/state/type IDs beforehand, and the reusable `structuredContent.id` for chaining. It does not cover auth/permissions or rate limits, but with annotations covering the safety profile this is a strong addition.

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 structured with prominent 'Quand', 'Plutôt que', bullet points, and 'Returns' sections. It is front-loaded with the core action and routing guidance, and every sentence carries useful information.

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 create mutation with full annotations and an output schema, the description covers purpose, sibling routing, non-idempotence, ID-resolution prerequisites, and return chaining. Nothing critical an agent needs in order 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 description coverage is 100%, so the schema already documents all 12 parameters, giving a baseline of 3. The description adds cross-parameter meaning by warning that relation IDs and state/type values are BoondManager numeric IDs that must be resolved first via entity searches or `boond://dictionary/*`, which helps agents supply valid values.

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: 'Crée un(e) facture dans BoondManager.' It also explicitly distinguishes this tool from `boond_invoices_update` and `boond_invoices_search`, so an agent can route correctly without opening schemas.

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?

Provides explicit when-to-use guidance ('Quand : pour ajouter une facture inexistant(e)') and names alternatives with their conditions: use `boond_invoices_update` to modify an existing record and `boond_invoices_search` first to check for duplicates.

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

Deploy Server