boondmanager-mcp-server

Créer une feuille de temps

boond_timesheets_create

Create a monthly timesheet (CRA) for a resource with day-by-day work and absence lines when none exists for that month. Provide resourceId and term, plus optional activity lines.

Instructions

Crée la feuille de temps (CRA) d'un mois pour une ressource, avec ses lignes jour par jour.

Quand : pour ouvrir le CRA d'un couple (ressource, mois) qui n'existe pas encore, après boond_timesheets_default. Plutôt que : boond_timesheets_search (startMonth/endMonth + resourceId) d'abord : l'API ne déduplique pas, deux CRA peuvent coexister sur le même mois ; boond_timesheets_update si le CRA existe déjà.

Un CRA est un conteneur mensuel (term + resource) ; les lignes vont dans regularTimes[] (production et absences) et exceptionalTimes[] — chaque ligne = un jour, une durée, un type d'unité d'œuvre, et pour la production un couple projectId / deliveryId imputable.
state n'est pas un champ d'écriture : il est piloté par le workflow de validation (boond_validations_search).
Écriture non idempotente. Modèle d'écriture établi en lecture depuis l'API (forme des CRA existants et de /times-reports/default), pas encore éprouvé en écriture sur un tenant de test — voir CLAUDE.md.

Returns : confirmation, ID créé (structuredContent.id) et fiche du CRA.

Input Schema

TableJSON Schema

Name	Required	Description
`term`	Yes	Mois du CRA (YYYY-MM). Un CRA = un mois × une ressource ; l'API ne déduplique pas.
`agencyId`	No	ID de l'agence — voir `boond_timesheets_default`. Déduite de la ressource si omise.
`resourceId`	Yes	ID de la ressource (le collaborateur dont c'est le CRA).
`regularTimes`	No	Lignes d'activité normale (production et absences). Omettre pour créer un CRA vide.
`exceptionalTimes`	No	Lignes d'activité exceptionnelle (interventions, astreintes) — types `exceptionalTime` / `exceptionalCalendar`.
`informationComments`	No	Commentaires du CRA.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Identifiant de l'entité créée/modifiée
`type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv2.17.0Sep 26, 2026

addedInput schema / properties / agencyId

Added value: +{
+  "description": "ID de l'agence — voir `boond_timesheets_default`. Déduite de la ressource si omise.",
+  "pattern": "^\\d+$",
+  "type": "string"
+}

removedInput schema / properties / endDate

Removed value: -{
-  "description": "Date de fin (YYYY-MM-DD)",
-  "type": "string"
-}

addedInput schema / properties / exceptionalTimes

Added value: +{
+  "description": "Lignes d'activité exceptionnelle (interventions, astreintes) — types `exceptionalTime` / `exceptionalCalendar`.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "batchId": {
+        "description": "ID du lot. Absent = aucun lot.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "deliveryId": {
+        "description": "ID de la prestation (delivery) imputée. Requis avec `projectId` pour la production — voir `boond_timesheets_default`.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "duration": {
+        "default": 1,
+        "description": "Durée en unités d'œuvre (jour par défaut : 1 = journée, 0.5 = demi-journée).",
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "projectId": {
+        "description": "ID du projet imputé. Requis pour une activité de production ; absent pour une absence. Couples autorisés : `boond_timesheets_default`.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "startDate": {
+        "description": "Jour saisi (YYYY-MM-DD). Doit tomber dans le mois `term` du CRA.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "workUnitTypeReference": {
+        "default": 1,
+        "description": "Code `reference` du type d'unité d'œuvre — voir `boond_timesheets_default` (`workUnitTypesAllowed` de la ressource). 1 = « Normale » (production) sur les tenants observés ; les absences (congés, RTT, maladie…) ont leurs propres codes.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "startDate"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / informationComments

Added value: +{
+  "description": "Commentaires du CRA.",
+  "type": "string"
+}

removedInput schema / properties / note

Removed value: -{
-  "description": "Notes",
-  "type": "string"
-}

removedInput schema / properties / projectId

Removed value: -{
-  "description": "ID du projet",
-  "type": "string"
-}

addedInput schema / properties / regularTimes

Added value: +{
+  "description": "Lignes d'activité normale (production et absences). Omettre pour créer un CRA vide.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "batchId": {
+        "description": "ID du lot. Absent = aucun lot.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "deliveryId": {
+        "description": "ID de la prestation (delivery) imputée. Requis avec `projectId` pour la production — voir `boond_timesheets_default`.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "duration": {
+        "default": 1,
+        "description": "Durée en unités d'œuvre (jour par défaut : 1 = journée, 0.5 = demi-journée).",
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "projectId": {
+        "description": "ID du projet imputé. Requis pour une activité de production ; absent pour une absence. Couples autorisés : `boond_timesheets_default`.",
+        "pattern": "^\\d+$",
+        "type": "string"
+      },
+      "startDate": {
+        "description": "Jour saisi (YYYY-MM-DD). Doit tomber dans le mois `term` du CRA.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "workUnitTypeReference": {
+        "default": 1,
+        "description": "Code `reference` du type d'unité d'œuvre — voir `boond_timesheets_default` (`workUnitTypesAllowed` de la ressource). 1 = « Normale » (production) sur les tenants observés ; les absences (congés, RTT, maladie…) ont leurs propres codes.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "startDate"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / resourceId / description

Previous value: -"ID de la ressource"New value: +"ID de la ressource (le collaborateur dont c'est le CRA)."

removedInput schema / properties / resourceId / minLength
```
Removed value: -1
```
addedInput schema / properties / resourceId / pattern
```
Added value: +"^\\d+$"
```

removedInput schema / properties / startDate

Removed value: -{
-  "description": "Date de début (YYYY-MM-DD)",
-  "type": "string"
-}

removedInput schema / properties / state

Removed value: -{
-  "description": "État de la feuille de temps",
-  "type": "string"
-}

changedInput schema / properties / term / description

Previous value: -"Mois au format YYYY-MM"New value: +"Mois du CRA (YYYY-MM). Un CRA = un mois × une ressource ; l'API ne déduplique pas."

removedInput schema / properties / totalDays

Removed value: -{
-  "description": "Total jours",
-  "type": "number"
-}

removedInput schema / properties / totalHours

Removed value: -{
-  "description": "Total heures",
-  "type": "number"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Identifiant de l'entité créée/modifiée",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds valuable behavioral context: 'Écriture non idempotente', the fact that 'state' is not a writable field and is controlled by the validation workflow, and the caveat that the write model is established from reading the API but not yet proven on a test tenant. This goes beyond what annotations provide, though it could have mentioned error behavior or side effects in more detail.

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: a one-sentence summary, a 'Quand' paragraph for usage, a 'Plutôt que' paragraph for alternatives, bullet points for key behavioral facts, and a 'Returns' line. Every sentence earns its place; no filler or repetition of schema details.

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?

Given the tool's complexity (6 parameters, two line-item arrays, non-idempotent writes, workflow interactions), the description covers all essential aspects: when to use, what to avoid, how lines are structured, what state means, and what the return value is. The output schema exists, so return values don't need further explanation. The only minor gap is the lack of explicit error scenarios, but that's not required for correct invocation.

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 schema already documents all parameters thoroughly. The description adds meaning by explaining the container concept ('Un CRA est un conteneur mensuel (term + resource)'), the distinction between regularTimes and exceptionalTimes, and the relationship to boond_timesheets_default for allowed project/delivery pairs and work unit types. It also clarifies that state is not a writable field, which is not obvious from the schema alone.

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 ('Crée'), a precise resource ('feuille de temps (CRA) d'un mois pour une ressource'), and the granularity ('avec ses lignes jour par jour'). It clearly distinguishes this from sibling tools by naming boond_timesheets_default, boond_timesheets_search, and boond_timesheets_update and explaining the exact role of each.

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 says when to use this tool ('pour ouvrir le CRA d'un couple (ressource, mois) qui n'existe pas encore, après boond_timesheets_default'), and when not to ('Plutôt que : boond_timesheets_search ... d'abord' and 'boond_timesheets_update si le CRA existe déjà'). It also warns about the API's non-deduplication behavior, which is critical for correct tool selection.

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

Deploy Server