boondmanager-mcp-server

Créer un(e) ressource

boond_resources_create

Create a new resource in BoondManager with name, contact, and job details. Returns confirmation, the new record ID, and full details, ready for chaining.

Instructions

Crée un(e) ressource dans BoondManager.

Quand : pour ajouter un(e) ressource inexistant(e). Plutôt que : boond_resources_update pour modifier un enregistrement existant, et boond_resources_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
`city`	No	Ville
`note`	No	Notes
`state`	No	État de la ressource
`title`	No	Titre / poste
`email1`	No	Email principal
`phone1`	No	Téléphone
`country`	No	Pays
`lastName`	Yes	Nom de famille
`firstName`	Yes	Prénom de la ressource/collaborateur

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.

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

Behavior4/5

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

Annotations already signal readOnly=false and idempotentHint=false; the description adds useful context by explaining that two identical calls will create two records and that relation/state/type IDs must be resolved beforehand via dictionary lookups. It could go further on permissions or other side effects, but the key behavioral caution is explicit.

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 well structured: a one-line purpose, then compact sections for when/alternatives, behavioral cautions, and return usage. No sentence is redundant with schema content, and the most important routing information is front-loaded.

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 create operation with two required fields, full schema descriptions, an output schema, and relevant sibling operations, this description covers when to use it, alternatives, duplicate behavior, ID resolution, and how to chain the result. Nothing necessary for correct invocation appears 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 coverage is 100% with each field described, so the baseline is 3. The description adds extra value beyond labels by telling the agent that relation/state/type values are numeric BoondManager IDs to resolve beforehand, which matters for correctly populating fields like state.

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 'Crée un(e) ressource dans BoondManager', a specific verb+resource statement, then adds 'pour ajouter un(e) ressource inexistant(e)'. It clearly distinguishes itself from update and search operations among the resource 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?

It provides an explicit 'Quand' (when to use) and 'Plutôt que' (instead of) section, naming boond_resources_update for modifications and instructing to run boond_resources_search first to avoid duplicates. This gives an agent concrete routing guidance and preconditions.

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

Deploy Server