boondmanager-mcp-server

Modifier un(e) produit

boond_products_update

Idempotent

Update an existing product by ID, modifying only specified fields like name, price, or tax rate. Preserves other data while replacing array fields.

Instructions

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

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_products_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 du produit à modifier
`name`	No	Nom du produit
`note`	No	Description
`state`	No	État
`taxRate`	No	Taux de TVA (%)
`reference`	No	Référence
`unitPrice`	No	Prix unitaire HT

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.17.0Sep 26, 2026
- removedInput schema / properties / id / minLength
```
Removed value: -1
```
- addedInput schema / properties / id / pattern
```
Added value: +"^\\d+$"
```

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

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, the description discloses partial-update semantics, array-field replacement behavior, and a rights-check strategy using boond_rights_get to avoid 403s. It also states the return value. Nothing contradicts the readOnlyHint=false, destructiveHint=false, or idempotentHint=true 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?

The description is compact and well-structured: purpose, usage context, behavioral caveats, and return value each get a short, scannable block. Every sentence adds operational value without filler.

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 an update tool with 7 parameters and an output schema, the description covers everything needed to call it correctly: identification by ID, when to choose it, partial-update caveats, a permission pre-check suggestion, and the response shape. The output schema supplies the detailed response structure, so no additional return documentation is needed.

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?

The input schema already documents all 7 parameters, so the baseline is 3. The description adds useful cross-cutting parameter behavior: only supplied fields are written, and array-type fields are replaced rather than merged, which goes beyond the schema's per-field descriptions.

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-object statement, 'Met à jour un(e) produit existant(e), identifié(e) par son ID', making the resource and action unmistakable. It also distinguishes itself from boond_products_create by explicitly saying that create is for records that do not exist yet.

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 provides an explicit 'Quand' condition ('modifier quelques champs d'un enregistrement déjà en base') and an explicit alternative ('Plutôt que boond_products_create si l'enregistrement n'existe pas encore'). This gives an agent clear when-to-use and when-not-to-use guidance.

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

Deploy Server