boondmanager-mcp-server

Reporting plans de production

boond_reporting_production_plans

Read-onlyIdempotent

Get aggregated production-plan KPIs (revenue, margin, rate, volumes) by scope and date range to analyze availability and positioning totals without listing individual records.

Instructions

Reporting des plans de production (disponibilités, positionnements...).

Quand : pour obtenir des agrégats (CA, marge, taux, volumes) sur un périmètre et une période. Plutôt que : boond_positionings_search pour la liste des enregistrements eux-mêmes : ce reporting renvoie des totaux calculés, pas les lignes qui les composent.

Filtres clés : périmètre (perimeterDynamic / perimeterManagers / perimeterAgencies…), période (period, periodDynamic), resourceTypes, resourceStates, positioningStates, positioningPeriod, showContracts, projects/contacts/companies.

⚠️ startDate + endDate (YYYY-MM-DD) sont REQUIS : l'API répond 422 sans eux.
Sans filtre de périmètre, l'agrégation porte sur tout le périmètre autorisé du compte — un total « entreprise » là où l'utilisateur attendait souvent son équipe.
Les états et types sont des ID entiers du dictionnaire (boond_application_dictionary), pas des libellés.
Une agrégation large peut durer plusieurs dizaines de secondes ; l'avancement est signalé via notifications/progress quand le client fournit un progressToken.

Returns : tableau d'indicateurs agrégés, rendu en texte. Lecture seule.

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)
`endDate`	Yes	Date de fin (YYYY-MM-DD). Requis par l'API.
`contacts`	No	Filtrer sur ces IDs de contacts.
`keywords`	No	Mots-clés.
`pageSize`	No	Nombre de résultats par page (max: 500, défaut: 30)
`projects`	No	Filtrer sur ces IDs de projets.
`useCache`	No	Cache de reporting : 'withCache' (valeurs mises en cache) ou 'withoutCache' (recalcul, défaut).
`companies`	No	Filtrer sur ces IDs de sociétés.
`startDate`	Yes	Date de début (YYYY-MM-DD). Requis par l'API.
`scorecards`	No	IDs des scorecards (indicateurs) à retourner.
`periodDynamic`	No	Période dynamique relative à aujourd'hui (avec period='dynamicPeriod') : today, thisWeek, thisMonth, thisTrimester, thisSemester, thisYear, thisFiscalYear, yesterday, lastWeek, lastMonth, lastTrimester, lastSemester, lastYear, lastFiscalYear, tomorrow, nextWeek, nextMonth, nextTrimester, nextSemester, nextYear, nextFiscalYear, lastCustomPeriod, nextCustomPeriod.
`resourceTypes`	No	IDs de types de ressources (dictionnaire setting.typeOf.resource).
`showContracts`	No	Afficher les contrats associés.
`perimeterPoles`	No	IDs de pôles. Conserve les entités dont le responsable appartient à ces pôles.
`resourceStates`	No	IDs d'états de ressources (dictionnaire setting.state.resource).
`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.
`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.
`positioningPeriod`	No	'created' (positionnements créés entre les dates, défaut) ou 'running' (en cours sur la période).
`positioningStates`	No	IDs d'états de positionnement (dictionnaire setting.state.positioning).
`perimeterBusinessUnits`	No	IDs de business units. Conserve les entités dont le responsable appartient à ces BU.
`periodDynamicParameters`	No	Paramètres de la période personnalisée (utilisé avec periodDynamic=lastCustomPeriod/nextCustomPeriod).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.12.2Aug 14, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed21 schema fields changedv2.7.0Jun 19, 2026

addedInput schema / properties / companies

Added value: +{
+  "description": "Filtrer sur ces IDs de sociétés.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / contacts

Added value: +{
+  "description": "Filtrer sur ces IDs de contacts.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

changedInput schema / properties / endDate / description

Previous value: -"Date de fin YYYY-MM-DD. Requis."New value: +"Date de fin (YYYY-MM-DD). Requis par l'API."

addedInput schema / properties / narrowPerimeter

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

changedInput schema / properties / page / description

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

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 / periodDynamic

Added value: +{
+  "description": "Période dynamique relative à aujourd'hui (avec period='dynamicPeriod') : today, thisWeek, thisMonth, thisTrimester, thisSemester, thisYear, thisFiscalYear, yesterday, lastWeek, lastMonth, lastTrimester, lastSemester, lastYear, lastFiscalYear, tomorrow, nextWeek, nextMonth, nextTrimester, nextSemester, nextYear, nextFiscalYear, lastCustomPeriod, nextCustomPeriod.",
+  "type": "string"
+}

addedInput schema / properties / periodDynamicParameters

Added value: +{
+  "description": "Paramètres de la période personnalisée (utilisé avec periodDynamic=lastCustomPeriod/nextCustomPeriod).",
+  "type": "string"
+}

addedInput schema / properties / positioningPeriod

Added value: +{
+  "description": "'created' (positionnements créés entre les dates, défaut) ou 'running' (en cours sur la période).",
+  "enum": [
+    "created",
+    "running"
+  ],
+  "type": "string"
+}

addedInput schema / properties / positioningStates

Added value: +{
+  "description": "IDs d'états de positionnement (dictionnaire setting.state.positioning).",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / projects

Added value: +{
+  "description": "Filtrer sur ces IDs de projets.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / resourceStates

Added value: +{
+  "description": "IDs d'états de ressources (dictionnaire setting.state.resource).",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / resourceTypes

Added value: +{
+  "description": "IDs de types de ressources (dictionnaire setting.typeOf.resource).",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / scorecards

Added value: +{
+  "description": "IDs des scorecards (indicateurs) à retourner.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / showContracts

Added value: +{
+  "description": "Afficher les contrats associés.",
+  "type": "boolean"
+}

changedInput schema / properties / startDate / description

Previous value: -"Date de début YYYY-MM-DD. Requis."New value: +"Date de début (YYYY-MM-DD). Requis par l'API."

addedInput schema / properties / useCache

Added value: +{
+  "description": "Cache de reporting : 'withCache' (valeurs mises en cache) ou 'withoutCache' (recalcul, défaut).",
+  "enum": [
+    "withCache",
+    "withoutCache"
+  ],
+  "type": "string"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already signal read-only and non-destructive behavior. The description goes well beyond that: it warns that missing startDate/endDate triggers a 422, that omitting perimeter filters aggregates over the entire account, that states/types are dictionary integer IDs, and that large aggregations can take tens of seconds with progress signaled via notifications/progress. These are rich behavioral disclosures not present in the 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 long but tightly organized: purpose, when/alternative, key filters, then bullet-pointed caveats and return/pagination details. Every sentence adds a distinct piece of information, and the critical warnings (required dates, perimeter default) are front-loaded. There is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 23 parameters and no output schema, this description covers nearly everything an agent needs: purpose, usage, required params, default perimeter behavior, dictionary IDs, performance, progress, return type, and pagination. It falls short slightly because the return value is described only vaguely as 'tableau d'indicateurs agrégés, rendu en texte', and the phantom 'period' reference introduces ambiguity about which parameter is actually used.

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 description coverage is 100%, so the baseline is 3. The description adds real meaning on top: the critical 'no perimeter = whole account' semantic, the dictionary-ID requirement for state/type parameters, and pagination limits. It loses a point because it references a 'period' parameter that does not exist in the schema, potentially leading an agent to send an unknown property.

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: it reports production plans and returns aggregates (CA, marge, taux, volumes) for a perimeter and period. It also distinguishes itself from boond_positionings_search by explicitly noting this tool returns calculated totals, not the underlying lines, which separates it from the most likely sibling confusion.

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 clearly defines when to use this tool (for aggregates) and the 'Plutôt que' clause explicitly names the alternative boond_positionings_search and the condition that selects it (wanting the records themselves vs. totals). This is direct, actionable guidance with no inference required.

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

Deploy Server

Reporting plans de production

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools