Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Créer un(e) contact

boond_contacts_create

Create a new contact in BoondManager with name, email, phone, and company details. Use after searching to confirm the contact does not already exist.

Instructions

Crée un(e) contact dans BoondManager.

Quand : pour ajouter un(e) contact inexistant(e). Plutôt que : boond_contacts_update pour modifier un enregistrement existant, et boond_contacts_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
NameRequiredDescriptionDefault
cityNoVille
noteNoNotes
titleNoTitre / fonction
email1NoEmail principal
phone1NoTéléphone
countryNoPays
lastNameYesNom de famille
companyIdNoID de la société associée
firstNameYesPrénom du contact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoIdentifiant de l'entité créée/modifiée
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.17.0
    • addedInput schema / properties / companyId / pattern
      Added value: +"^\\d+$"
  2. Changed1 schema field changedv2.15.0
    • 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,}$"
  3. Changed2 schema fields changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Changed1 schema field changedv2.7.0
    • 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"
+}
  5. First observedv2.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Although annotations already indicate idempotentHint=false, the description elaborates that two identical calls create two records because the API does not deduplicate, which is practically useful. It also discloses that relation IDs are numeric BoondManager IDs that must be resolved beforehand—information not available from 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, when to use, alternatives, behavioral caveats, and return value handling are each given one or two sentences. Every line carries information, and the core purpose 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?

It covers the essential aspects: what it does, when to use it (and when not to), non-idempotence, relational ID resolution, and the structure of success output (confirmation, created ID, complete record, reusable 'structuredContent.id'). Given an output schema exists Sweater, nothing critical is 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?

The schema has 100% coverage with descriptions for all 9 parameters, so the baseline is 3. The description adds a valuable general rule: relation IDs and states/types are numeric BoondManager IDs that need pre-resolution via entity searches or 'boond://dictionary/*'. This clarifies how to correctly populate fields like companyId, pushing semantics above baseline.

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) contact dans BoondManager', stating a specific verb and resource. It explicitly distinguishes itself from 'boond_contacts_update' (for modifying) and 'boond_contacts_search' (for pre-checking existence), making its purpose unambiguous relative to 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?

The 'Quand' clause states to use this tool when adding a contact that does not yet exist. The 'Plutôt que' clause explicitly names alternatives: 'boond_contacts_update' for existing records and 'boond_contacts_search' for prior verification. This is clear when/when-not guidance with specific siblings.

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

Deploy Server

Other Tools