boondmanager-mcp-server

Modifier un(e) candidat

boond_candidates_update

Idempotent

Update an existing candidate record by ID, modifying only the fields provided while leaving all other fields unchanged.

Instructions

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

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_candidates_create si l'enregistrement n'existe pas encore, ou boond_find pour résoudre un nom / un e-mail en ID.

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 candidat à modifier
`city`	No	Ville
`note`	No	Notes
`town`	No	Ville, telle que stockée par l'onglet Information (`town`)
`state`	No	État du candidat
`title`	No	Titre / fonction
`email1`	No	Email principal
`phone1`	No	Téléphone
`address`	No	Adresse (rue et numéro)
`country`	No	Pays
`lastName`	No	Nom
`postcode`	No	Code postal
`firstName`	No	Prénom
`mainSkills`	No	Compétences principales
`availability`	No	Disponibilité : ID numérique du dictionnaire `setting.availability`
`mobilityAreas`	No	Zones de mobilité : IDs du dictionnaire `setting.mobilityArea` (ex: 'mondeeuropebelgique'). Remplace la liste existante : relire l'onglet Information et fusionner avant d'appeler.
`globalEvaluation`	No	Évaluation globale : ID du dictionnaire `setting.evaluation` (ex: 'a', 'b', 'c', 'd')
`informationComments`	No	Commentaires de l'onglet Information

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.18.0Oct 2, 2026

addedInput schema / properties / address

Added value: +{
+  "description": "Adresse (rue et numéro)",
+  "type": "string"
+}

addedInput schema / properties / availability

Added value: +{
+  "description": "Disponibilité : ID numérique du dictionnaire `setting.availability`",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / globalEvaluation

Added value: +{
+  "description": "Évaluation globale : ID du dictionnaire `setting.evaluation` (ex: 'a', 'b', 'c', 'd')",
+  "type": "string"
+}

addedInput schema / properties / informationComments

Added value: +{
+  "description": "Commentaires de l'onglet Information",
+  "type": "string"
+}

addedInput schema / properties / mobilityAreas

Added value: +{
+  "description": "Zones de mobilité : IDs du dictionnaire `setting.mobilityArea` (ex: 'mondeeuropebelgique'). Remplace la liste existante : relire l'onglet Information et fusionner avant d'appeler.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / postcode

Added value: +{
+  "description": "Code postal",
+  "type": "string"
+}

addedInput schema / properties / town

Added value: +{
+  "description": "Ville, telle que stockée par l'onglet Information (`town`)",
+  "type": "string"
+}

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

Changed1 schema field changedv2.15.0Sep 10, 2026

changedInput schema / properties / email1 / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

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?

Annotations already declare write/idempotent/non-destructive, and the description adds real behavioral nuance beyond them: partial-update semantics (only supplied fields are written, others left in place), the warning that array fields are replaced not merged, and the guidance to pre-flight with boond_rights_get to avoid a 403. These are the kind of hidden behaviors an agent cannot infer from the schema.

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 verb+resource sentence, then a compact Quand/Plutôt que block and three short bullets. Every line carries distinct, actionable information with no 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?

Covers purpose, alternatives, partial-update and array-replacement edge cases, and permission pre-checking; an output schema exists so return values need no elaboration. For an 18-parameter mutation tool this is complete enough to call 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 coverage is 100% so the schema documents every parameter and the baseline is 3; the description adds cross-parameter semantics the schema does not (only provided fields are written; array params overwrite rather than append), which justifies the bump. It does not add per-parameter format or dictionary detail beyond what the schema already carries.

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 ("Met à jour") and resource ("candidat existant"), and the identifying key ("son ID"). It explicitly distinguishes itself from boond_candidates_create and boond_find, so an agent can select it without opening any 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?

Provides an explicit "Quand" clause (modify a few fields of an existing record) and a "Plutôt que" clause naming the exact alternatives for the non-existing case (create) and the name/email-to-ID resolution case (boond_find). Both the when and the when-not are covered.

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

Deploy Server