boondmanager-mcp-server

Rechercher des bons de commande

boond_orders_search

Read-onlyIdempotent

Search purchase orders in BoondManager with filters like company, project, status, and date. Track customer orders and spot discrepancies against billed amounts.

Instructions

Recherche des bons de commande dans BoondManager avec filtres par société et projet.

Quand : pour suivre les bons de commande client. Plutôt que : boond_invoices_search pour la facturation qui en découle, boond_orders_get si l'ID est connu.

companyId / projectId sont convertis en références keywords (CSOC / PRJ) : l'API n'a pas de paramètre dédié.

Returns: Liste des bons de commande correspondants.

fields : projection côté MCP, jamais transmise à l'API — remplace le résumé par les seuls attributs listés (noms inconnus ignorés). À utiliser sur les grosses pages.
Pagination : pageSize 1–500 (défaut 30), page 1–100 — au-delà : refus, affiner les filtres.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Numéro de page (défaut: 1, max: 100)
`sort`	No	Champ de tri (ex: lastName, firstName, updateDate)
`flags`	No	IDs de drapeaux (flags) — `boond_flags_search`.
`order`	No	Ordre de tri (asc/desc)
`fields`	No	Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
`period`	No	Champ de date borné par `startDate` / `endDate` : created, updated, period (période couverte).
`states`	No	IDs d'états de bon de commande — `boond://dictionary/states/orders`.
`endDate`	No	Date de fin (YYYY-MM-DD), à utiliser avec `period`.
`keywords`	No	Mots-clés de recherche
`pageSize`	No	Nombre de résultats par page (max: 500, défaut: 30)
`companies`	No	IDs de sociétés (filtre API natif, équivalent de `companyId` pour plusieurs sociétés).
`companyId`	No	Filtrer par ID société (référence keywords CSOC<id>)
`contactId`	No	Filtrer par ID contact (référence keywords CCON<id>)
`projectId`	No	Filtrer par ID projet (référence keywords PRJ<id>)
`startDate`	No	Date de début (YYYY-MM-DD), à utiliser avec `period`.
`projectTypes`	No	IDs de types de projet — `boond://dictionary/typeOf/projects`.
`periodDynamic`	No	Fenêtre relative appliquée à `period` (à la place de `startDate` / `endDate`) : today, thisWeek, thisMonth, lastMonth, thisYear, untilToday…
`paymentMethods`	No	IDs de modes de paiement — `boond://dictionary/paymentMethods`.
`perimeterPoles`	No	IDs de pôles. Conserve les entités dont le responsable appartient à ces pôles.
`narrowPerimeter`	No	Si true, jointure ET entre les filtres `perimeter*` (au lieu de OU par défaut).
`perimeterDynamic`	No	Périmètre dynamique relatif à l'utilisateur courant (raccourci sans avoir à connaître son propre ID). Valeurs : 'data' (mes propres données), 'managers' (mon équipe / mes N-1), 'agencies' (mes agences), 'poles' (mes pôles), 'businessUnits' (mes BU). Combinable.
`customerAgreement`	No	true = accord client reçu uniquement, false = sans accord.
`perimeterAgencies`	No	IDs d'agences. Conserve les entités dont le responsable appartient à ces agences.
`perimeterManagers`	No	IDs des managers (ressources). Conserve les entités dont le responsable est l'un de ces managers. Pour 'mon équipe / N-1 d'une personne X', passer [X_id]. Obtenir son propre ID via boond_application_current_user.
`perimeterBusinessUnits`	No	IDs de business units. Conserve les entités dont le responsable appartient à ces BU.
`exceededOrderedTurnover`	No	true = commandes dont le facturé dépasse le montant commandé.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Nombre d'éléments retournés sur cette page
`items`	Yes
`total`	No	Nombre total de résultats côté BoondManager

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv2.17.0Sep 26, 2026

addedInput schema / properties / companies

Added value: +{
+  "description": "IDs de sociétés (filtre API natif, équivalent de `companyId` pour plusieurs sociétés).",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

changedInput schema / properties / companyId / description

Previous value: -"Filtrer par ID société"New value: +"Filtrer par ID société (référence keywords CSOC<id>)"

addedInput schema / properties / companyId / pattern
```
Added value: +"^\\d+$"
```

addedInput schema / properties / contactId

Added value: +{
+  "description": "Filtrer par ID contact (référence keywords CCON<id>)",
+  "pattern": "^\\d+$",
+  "type": "string"
+}

addedInput schema / properties / customerAgreement

Added value: +{
+  "description": "true = accord client reçu uniquement, false = sans accord.",
+  "type": "boolean"
+}

addedInput schema / properties / endDate

Added value: +{
+  "description": "Date de fin (YYYY-MM-DD), à utiliser avec `period`.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / exceededOrderedTurnover

Added value: +{
+  "description": "true = commandes dont le facturé dépasse le montant commandé.",
+  "type": "boolean"
+}

addedInput schema / properties / flags

Added value: +{
+  "description": "IDs de drapeaux (flags) — `boond_flags_search`.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / narrowPerimeter

Added value: +{
+  "description": "Si true, jointure ET entre les filtres `perimeter*` (au lieu de OU par défaut).",
+  "type": "boolean"
+}

addedInput schema / properties / order

Added value: +{
+  "description": "Ordre de tri (asc/desc)",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

changedInput schema / properties / page / description

Previous value: -"Numéro de page (max: 100)"New value: +"Numéro de page (défaut: 1, max: 100)"

changedInput schema / properties / pageSize / description

Previous value: -"Résultats par page"New value: +"Nombre de résultats par page (max: 500, défaut: 30)"

addedInput schema / properties / paymentMethods

Added value: +{
+  "description": "IDs de modes de paiement — `boond://dictionary/paymentMethods`.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / perimeterAgencies

Added value: +{
+  "description": "IDs d'agences. Conserve les entités dont le responsable appartient à ces agences.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / perimeterBusinessUnits

Added value: +{
+  "description": "IDs de business units. Conserve les entités dont le responsable appartient à ces BU.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / perimeterDynamic

Added value: +{
+  "description": "Périmètre dynamique relatif à l'utilisateur courant (raccourci sans avoir à connaître son propre ID). Valeurs : 'data' (mes propres données), 'managers' (mon équipe / mes N-1), 'agencies' (mes agences), 'poles' (mes pôles), 'businessUnits' (mes BU). Combinable.",
+  "items": {
+    "enum": [
+      "data",
+      "agencies",
+      "poles",
+      "businessUnits",
+      "managers"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / perimeterManagers

Added value: +{
+  "description": "IDs des managers (ressources). Conserve les entités dont le responsable est l'un de ces managers. Pour 'mon équipe / N-1 d'une personne X', passer [X_id]. Obtenir son propre ID via boond_application_current_user.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / perimeterPoles

Added value: +{
+  "description": "IDs de pôles. Conserve les entités dont le responsable appartient à ces pôles.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / period

Added value: +{
+  "description": "Champ de date borné par `startDate` / `endDate` : created, updated, period (période couverte).",
+  "enum": [
+    "created",
+    "updated",
+    "period"
+  ],
+  "type": "string"
+}

addedInput schema / properties / periodDynamic

Added value: +{
+  "description": "Fenêtre relative appliquée à `period` (à la place de `startDate` / `endDate`) : today, thisWeek, thisMonth, lastMonth, thisYear, untilToday…",
+  "enum": [
+    "today",
+    "yesterday",
+    "tomorrow",
+    "thisWeek",
+    "lastWeek",
+    "nextWeek",
+    "thisMonth",
+    "lastMonth",
+    "nextMonth",
+    "thisTrimester",
+    "lastTrimester",
+    "nextTrimester",
+    "thisSemester",
+    "lastSemester",
+    "nextSemester",
+    "thisYear",
+    "lastYear",
+    "nextYear",
+    "thisFiscalYear",
+    "lastFiscalYear",
+    "nextFiscalYear",
+    "untilToday"
+  ],
+  "type": "string"
+}

changedInput schema / properties / projectId / description

Previous value: -"Filtrer par ID projet"New value: +"Filtrer par ID projet (référence keywords PRJ<id>)"

addedInput schema / properties / projectId / pattern
```
Added value: +"^\\d+$"
```

addedInput schema / properties / projectTypes

Added value: +{
+  "description": "IDs de types de projet — `boond://dictionary/typeOf/projects`.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Champ de tri (ex: lastName, firstName, updateDate)",
+  "type": "string"
+}

addedInput schema / properties / startDate

Added value: +{
+  "description": "Date de début (YYYY-MM-DD), à utiliser avec `period`.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / states

Added value: +{
+  "description": "IDs d'états de bon de commande — `boond://dictionary/states/orders`.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

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.9.0Aug 3, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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": {
+    "count": {
+      "description": "Nombre d'éléments retournés sur cette page",
+      "type": "number"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attributes": {
+            "additionalProperties": {},
+            "description": "Attributs projetés (présent si `fields` est fourni)",
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "description": "Résumé standard (absent si `fields` est fourni)",
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Nombre total de résultats côté BoondManager",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "items"
+  ],
+  "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 mark the tool as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail: companyId/projectId are converted to keyword references because the API has no dedicated parameter, fields is a MCP-side projection never sent to the API, and pagination beyond pageSize 500/page 100 is refused. This goes well beyond the structured 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 front-loaded with purpose, then usage, then key operational notes in compact bullets. It is appropriately sized for a 26-parameter tool, with no wasted sentences aside from a minor redundant 'Returns' line already covered by the output schema.

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 complex search tool, the description covers purpose, sibling differentiation, core filter semantics, projection behavior, and pagination constraints. The rich input schema and output schema cover the remaining parameters and return shape, so nothing essential 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?

Schema coverage is 100%, so the schema carries most parameter documentation. The description still adds meaningful context by explaining the keyword conversion mechanism for companyId/projectId, the MCP-side behavior of fields, and the hard pagination limits with advice to refine filters.

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 states a specific verb and resource: 'Recherche des bons de commande dans BoondManager avec filtres par société et projet.' It also distinguishes itself from boond_invoices_search and boond_orders_get, which helps an agent select the right tool among many order-related 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 description provides an explicit 'Quand' section (for tracking client purchase orders) and a 'Plutôt que' section naming boond_invoices_search for downstream invoicing and boond_orders_get when the ID is already known. This gives clear when-to-use and when-not-to-use guidance with alternatives.

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

Deploy Server