boondmanager-mcp-server

Reporting projets

boond_reporting_projects

Read-onlyIdempotent

Compute aggregated project totals (revenue, margin, profitability) over a chosen scope and period to get key KPIs without retrieving individual project records.

Instructions

Reporting des projets (CA, marge, rentabilité...).

Quand : pour obtenir des agrégats (CA, marge, taux, volumes) sur un périmètre et une période. Plutôt que : boond_projects_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), projectTypes, projectStates, resources, projects, contacts, companies, maxProjects.

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`	No	Date de fin (YYYY-MM-DD).
`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.
`resources`	No	Filtrer sur ces IDs de ressources.
`startDate`	No	Date de début (YYYY-MM-DD).
`scorecards`	No	IDs des scorecards (indicateurs) à retourner.
`maxProjects`	No	Nombre de projets par page (1-10, défaut 1). Le nombre de résultats = projets × indicateurs.
`projectTypes`	No	IDs de types de projets (dictionnaire setting.typeOf.project).
`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.
`projectStates`	No	IDs d'états de projets (dictionnaire setting.state.project).
`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.
`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.
`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#"
```

Changed20 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."New value: +"Date de fin (YYYY-MM-DD)."

addedInput schema / properties / maxProjects

Added value: +{
+  "description": "Nombre de projets par page (1-10, défaut 1). Le nombre de résultats = projets × indicateurs.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}

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

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

addedInput schema / properties / projectTypes

Added value: +{
+  "description": "IDs de types de projets (dictionnaire setting.typeOf.project).",
+  "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 / resources

Added value: +{
+  "description": "Filtrer sur ces IDs de ressources.",
+  "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"
+}

changedInput schema / properties / startDate / description

Previous value: -"Date de début YYYY-MM-DD."New value: +"Date de début (YYYY-MM-DD)."

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"
+}

Addedv2.2.0Jun 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: the default perimeter is the entire authorized account scope, aggregation can take tens of seconds with progress signaled via notifications/progress, and pagination limits are enforced (pageSize 1-500, page 1-100). It also notes the return is rendered as text. This is strong supplementary behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Quand, Plutôt que, Filtres clés, Returns, Pagination) and front-loads the core purpose. It is longer than average, but the length is justified given 22 parameters and the need to explain perimeter semantics, dictionary IDs, and performance characteristics. Every section earns its place; 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 complex reporting tool with 22 parameters, no required params, and no output schema, the description covers the essential behavioral aspects: what it returns, how to filter, the default scope trap, performance expectations, and pagination constraints. It doesn't detail the exact structure of the returned indicators, but since there is no output schema and the description says 'tableau d'indicateurs agrégés, rendu en texte', an agent has enough to call it correctly. The reference to boond_application_dictionary for IDs is a useful pointer.

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 meaningful semantic context beyond the schema: it groups filters into perimeter vs period vs project filters, explains that perimeterDynamic is a shortcut for the current user, clarifies that projectTypes/projectStates are dictionary IDs (not labels), and explains the maxProjects multiplication effect ('projets × indicateurs'). It also warns about the default perimeter behavior, which is critical for correct use. This exceeds the 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 a clear statement: 'Reporting des projets (CA, marge, rentabilité...)' and explicitly contrasts itself with boond_projects_search, which returns raw records. It names the resource (projects), the operation (aggregated reporting), and the key metrics (CA, marge, taux, volumes). This distinguishes it from sibling reporting tools like boond_reporting_companies and boond_reporting_resources by the resource being aggregated.

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 explicitly states when to use it ('Quand : pour obtenir des agrégats...') and when not to ('Plutôt que : boond_projects_search pour la liste des enregistrements eux-mêmes'). It also provides key filter guidance, warns about the default perimeter behavior, and explains the dictionary ID requirement for states/types. This is comprehensive routing guidance.

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

Deploy Server

Reporting projets

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools