boondmanager-mcp-server

Reporting ressources

boond_reporting_resources

Read-onlyIdempotent

Get aggregated resource metrics (occupancy rate, revenue, productivity) for a selected scope and period. Returns calculated totals instead of individual records, with filters for perimeter, time range, resource types, and states.

Instructions

Reporting des ressources (taux d'occupation, CA, productivité...).

Quand : pour obtenir des agrégats (CA, marge, taux, volumes) sur un périmètre et une période. Plutôt que : boond_resources_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), reportingCategory, resourceTypes, resourceStates, period, resources/projects/contacts/companies, maxResources.

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)
`period`	No	Découpage temporel : 'onePeriod' (unique, entre startDate/endDate), 'dynamicPeriod' (selon periodDynamic), 'monthly' (6 mois depuis startDate), 'quarterly', 'semiAnnual', 'annual'. La synthèse accepte aussi 'weekly'.
`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.
`maxResources`	No	Nombre de ressources par page (1-10, défaut 1). Le nombre de résultats = ressources × indicateurs.
`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).
`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.
`reportingCategory`	No	Vue : 'showByResources' (défaut, sans returnedPeriod) ou 'showByPeriods' (returnedPeriod requis).
`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#"
```

Changed23 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)."

addedInput schema / properties / maxResources

Added value: +{
+  "description": "Nombre de ressources par page (1-10, défaut 1). Le nombre de résultats = ressources × 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 / period

Added value: +{
+  "description": "Découpage temporel : 'onePeriod' (unique, entre startDate/endDate), 'dynamicPeriod' (selon periodDynamic), 'monthly' (6 mois depuis startDate), 'quarterly', 'semiAnnual', 'annual'. La synthèse accepte aussi 'weekly'.",
+  "type": "string"
+}

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

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

addedInput schema / properties / reportingCategory

Added value: +{
+  "description": "Vue : 'showByResources' (défaut, sans returnedPeriod) ou 'showByPeriods' (returnedPeriod requis).",
+  "enum": [
+    "showByResources",
+    "showByPeriods"
+  ],
+  "type": "string"
+}

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 / 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. Requis."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"
+}

removedInput schema / required

Removed value: -[
-  "startDate",
-  "endDate"
-]

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?

Even with annotations indicating readOnlyHint, idempotentHint, and non-destructive, the description adds critical behavioral context: it clarifies that the aggregation spans the entire authorized perimeter if no filter is given (a common pitfall), warns about potentially long execution times, mentions progress notifications via progressToken, and notes that response is text-rendered. This goes beyond the annotations to set correct expectations.

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 sections: purpose, when to use, key filters, warnings, returns, and pagination. It is front-loaded with the most critical information (purpose and distinction) and each sentence serves a purpose. No fluff, and it remains readable despite its length.

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 tool with 24 parameters and no output schema, the description covers all essential aspects: purpose, usage, behavioral caveats, parameter hints, and output format (returned as text). It also mentions progress tracking and pagination constraints, which are critical for an agent to know. The description is complete enough for an agent to select and invoke it correctly without further context.

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 input schema already covers 100% of parameters with descriptions, so the baseline is 3. The description adds value by highlighting key filters like perimeter and period in a consolidated list, and clarifies that states/types are integer IDs from the dictionary (boond_application_dictionary), not labels. It also notes pagination limits and constraints (pageSize 1-500, page 1-100). This provides additional semantic meaning 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 clearly states the tool's purpose: it provides aggregated reporting metrics (occupancy rate, revenue, productivity) over a perimeter and period. It uses a specific verb ('Reporting') and resource ('ressources') and explicitly distinguishes itself from boond_resources_search for raw list retrieval. This makes it easy for an agent to understand what it does and how it differs from a similar sibling.

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: 'Quand' (when to use), 'Plutôt que' (rather than), and key filters. It clearly states that if you need the actual records, use boond_resources_search instead, and it warns about the default perimeter ('tout' the authorized account) and performance implications. This is comprehensive and actionable.

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

Deploy Server

Reporting ressources

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools