boondmanager-mcp-server

Créer un(e) projet

boond_projects_create

Create a new project in BoondManager with name, dates, client, contact, and type. Use after searching to avoid duplicates; returns the created record ID for chaining.

Instructions

Crée un(e) projet dans BoondManager.

Quand : pour ajouter un(e) projet inexistant(e). Plutôt que : boond_projects_update pour modifier un enregistrement existant, et boond_projects_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
`name`	Yes	Nom du projet / mission
`note`	No	Notes / description du projet
`state`	No	État du projet (0=en cours, 1=terminé, 2=archivé...)
`typeOf`	No	Type de projet (ID du dictionnaire setting.typeOf.project)
`endDate`	No	Date de fin (YYYY-MM-DD)
`companyId`	No	ID de la société cliente
`contactId`	No	ID du contact associé
`startDate`	No	Date de début (YYYY-MM-DD)
`opportunityId`	No	ID de l'opportunité liée

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.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.8.0Jun 29, 2026

addedInput schema / properties / typeOf

Added value: +{
+  "description": "Type de projet (ID du dictionnaire setting.typeOf.project)",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

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 states that the write is real and non-idempotent, that duplicate calls create duplicate records, and that relation/state/type IDs must be resolved beforehand. This adds concrete behavioral context that annotations alone do not convey.

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 with clear labels ('Quand', 'Plutôt que', 'Returns') and bullet points. Every sentence earns its place, and important behavioral notes are 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 tool with 9 parameters and an output schema, the description covers when to use it, when not to, key ID resolution requirements, non-idempotency, and return value usage. An agent has enough context to call the tool correctly and chain the resulting ID.

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 schema already covers all parameters (100% coverage), so the baseline is 3. The description adds useful shared semantics by explaining that relation IDs and state/type fields are numeric BoondManager IDs to resolve via searches or boond://dictionary/*, which is meaningful 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?

The description opens with a clear verb and resource ('Crée un projet dans BoondManager') and explicitly distinguishes itself from boond_projects_update and boond_projects_search. An agent can immediately identify what this tool does and how it differs from related project tools.

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 explicit usage guidance: use it to add a non-existent project, search first to avoid duplicates, and prefer update for existing records. This directly answers when to use the tool versus alternatives.

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

Deploy Server