boondmanager-mcp-server

Modifier un(e) ressource

boond_resources_update

Idempotent

Update an existing resource by ID with partial field updates. Modify only specified fields, replace array fields, and get confirmation with the updated record.

Instructions

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

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_resources_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 de la ressource à modifier
`city`	No	Ville
`note`	No	Notes
`state`	No	État
`title`	No	Titre / poste
`email1`	No	Email principal
`phone1`	No	Téléphone
`country`	No	Pays
`lastName`	No	Nom
`firstName`	No	Prénom

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+$"
```

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?

Adds valuable behavioral details beyond annotations: partial update semantics (only provided fields are written), array fields are replaced not merged, and a rights-check suggestion to avoid 403s. Annotations already carry idempotentHint and destructiveHint, but the description enriches operational understanding.

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?

Well-structured and economical: one-sentence purpose, clear usage guidance, targeted bullet points for behavior, and a returns note. No filler; every sentence carries operational 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?

Complete for an update tool: covers update target, when to use, partial update behavior, array caveat, rights check, and return value. With an output schema present, return details are not needed. An agent has everything necessary to 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?

The input schema already has 100% description coverage with field labels (e.g., 'Ville', 'État'). The description adds general parameter behavior—partial update and array replacement—which influences how fields are used, though it does not elaborate on individual field meanings beyond the schema.

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 explicitly that it updates an existing resource identified by its ID, and names boond_resources_create and boond_find as alternatives, distinguishing this update endpoint from creation and ID resolution. Clear verb+resource with sibling differentiation.

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' section and 'Plutôt que' alternatives, directing to create when the record doesn't exist and to find for name/email resolution. Also recommends checking rights via boond_rights_get before attempting, giving concrete preconditions.

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

Deploy Server