boondmanager-mcp-server

Rechercher des feuilles de temps

boond_timesheets_search

Read-onlyIdempotent

Search monthly timesheets (CRA) in BoondManager by month, resource, validation state, and perimeter. Filter by required date range (YYYY-MM) to retrieve matching timesheet summaries.

Instructions

Recherche des feuilles de temps (CRA mensuels) dans BoondManager, par mois, ressource, état de validation (validationStates : waitingForValidation / validated / rejected) et périmètre (perimeter*).

Quand : pour balayer les CRA de plusieurs ressources sur une période. Plutôt que : boond_resources_timesheets quand on part d'une ressource précise, et boond_timesheets_get pour le détail jour par jour d'un CRA.

⚠️ startMonth et endMonth (format YYYY-MM) sont requis par l'API — passer YYYY-MM-DD ou les omettre renvoie un 422.

Returns: Liste des feuilles de temps correspondantes (une ligne par CRA : mois, période, statut, totaux).

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)
`order`	No	Ordre de tri (asc/desc)
`closed`	No	true = CRA clôturés uniquement, false = non clôturés.
`fields`	No	Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
`endMonth`	Yes	Mois de fin au format YYYY-MM (ex: '2025-03'). Requis.
`keywords`	No	Mots-clés (préfixes 'TPS', 'COMP'...).
`pageSize`	No	Nombre de résultats par page (max: 500, défaut: 30)
`resourceId`	No	Filtrer par ID ressource (référence keywords COMP<id>)
`startMonth`	Yes	Mois de début au format YYYY-MM (ex: '2025-01'). Requis.
`resourceTypes`	No	IDs de types de ressource — `boond://dictionary/typeOf/resources`.
`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.
`validationStates`	No	États du workflow de validation : waitingForValidation (à valider), validated, rejected.
`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.

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.

Changed15 schema fields changedv2.17.0Sep 26, 2026

addedInput schema / properties / closed

Added value: +{
+  "description": "true = CRA clôturés uniquement, false = non clôturés.",
+  "type": "boolean"
+}

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

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

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

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

addedInput schema / properties / resourceTypes

Added value: +{
+  "description": "IDs de types de ressource — `boond://dictionary/typeOf/resources`.",
+  "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 / validationStates

Added value: +{
+  "description": "États du workflow de validation : waitingForValidation (à valider), validated, rejected.",
+  "items": {
+    "enum": [
+      "waitingForValidation",
+      "validated",
+      "rejected"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

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

TDQS

A4.6/5.0

Behavior4/5

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

The description goes beyond the readOnly/idempotent annotations by disclosing the 422 error on incorrect date format, the return structure (one line per CRA), the fields projection behavior (not sent to API, unknown names ignored), and pagination limits. These are valuable behavioral details not captured in annotations.

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 (purpose, when, instead, warning, returns, fields, pagination) and front-loads the core purpose. It is slightly verbose but every sentence contributes useful information, making it appropriately sized for an 18-parameter tool.

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 tool with 18 parameters and an output schema, the description covers usage context, alternatives, error conditions, return format, projection behavior, and pagination constraints. It leaves no critical gaps for an agent to correctly select and invoke the tool.

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?

With 100% schema coverage, the schema already documents all parameters. The description adds meaning by clarifying the fields projection is MCP-side (not passed to API) and specifying pagination ranges, which enhances understanding beyond the schema. It does not duplicate existing schema descriptions.

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 feuilles de temps (CRA mensuels) dans BoondManager') and explicitly distinguishes itself from siblings: it is for scanning multiple resources over a period, versus boond_resources_timesheets for a specific resource and boond_timesheets_get for day-by-day detail. This makes the tool's role unambiguous.

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?

It provides explicit 'Quand' (when to use) and 'Plutôt que' (instead of) sections, naming the exact alternatives and the conditions that select them. It also includes a warning about required month format that prevents misuse.

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

Deploy Server