Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Creer une demande d'absence

boond_absences_create

Create an absence request (paid leave, RTT, sickness) for a resource using its ID. The request is submitted for validation and returns the created leave details.

Instructions

Crée une demande d'absence (congés, RTT, maladie…) pour une ressource.

Quand : pour poser une absence au nom d'une ressource identifiée par son ID. Plutôt que : boond_absences_update pour modifier une demande déjà déposée.

  • Le détail est porté par absencesPeriods ; si le tableau est omis, une période unique est déduite de startDate/endDate.

  • Pas de state : sur /absences-reports l'état est une chaîne du workflow de validation (waitingForValidation, validated…) que seul le workflow déplace — la demande part en attente de validation, elle n'est pas validée par cet appel (suivi via boond_validations_search).

  • Écriture non idempotente — l'API ne déduplique pas deux demandes sur les mêmes dates.

Returns : confirmation et fiche de la demande créée.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoCommentaire / motif
typeOfYesLibellé de l'absence (congé payé, RTT, maladie, sans solde...) — porté par `title` ; le type effectif est `workUnitTypeReference`.
endDateYesDate de fin (YYYY-MM-DD)
durationNoDurée en jours ; calculée automatiquement si absente
startDateYesDate de début (YYYY-MM-DD)
resourceIdYesID de la ressource en absence
absencesPeriodsNoPériodes d'absence Boond brutes
workUnitTypeReferenceNoCode `reference` du type d'absence, publié par `boond_absences_default` (`workUnitTypesAllowed` de la ressource : RTT, maladie, congés payés…) — nulle part ailleurs. Défaut 1 (à confirmer avec le default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.17.0
    • removedInput schema / properties / resourceId / minLength
      Removed value: -1
    • addedInput schema / properties / resourceId / pattern
      Added value: +"^\\d+$"
    • removedInput schema / properties / state
      Removed value: -{
-  "description": "État de la demande (0=en attente, 1=validé, 2=refusé...)",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • changedInput schema / properties / typeOf / description
      Previous value: -"Libellé de l'absence (congé payé, RTT, maladie, sans solde...)"New value: +"Libellé de l'absence (congé payé, RTT, maladie, sans solde...) — porté par `title` ; le type effectif est `workUnitTypeReference`."
    • changedInput schema / properties / workUnitTypeReference / description
      Previous value: -"Référence du type d'unité d'absence, défaut 1"New value: +"Code `reference` du type d'absence, publié par `boond_absences_default` (`workUnitTypesAllowed` de la ressource : RTT, maladie, congés payés…) — nulle part ailleurs. Défaut 1 (à confirmer avec le default)."
  2. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed4 schema fields changedv2.8.0
    • addedInput schema / properties / absencesPeriods
      Added value: +{
+  "description": "Périodes d'absence Boond brutes",
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / duration
      Added value: +{
+  "description": "Durée en jours ; calculée automatiquement si absente",
+  "type": "number"
+}
    • changedInput schema / properties / typeOf / description
      Previous value: -"Type d'absence (congé payé, RTT, maladie, sans solde...)"New value: +"Libellé de l'absence (congé payé, RTT, maladie, sans solde...)"
    • addedInput schema / properties / workUnitTypeReference
      Added value: +{
+  "description": "Référence du type d'unité d'absence, défaut 1",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
  4. First observedv2.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing that the call is non-idempotent, that the API does not deduplicate requests on the same dates, and that the created absence starts in a waiting-for-validation state rather than being immediately validated. These are important behavioral traits an agent needs to know.

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 for when to use, what to use instead, key behavioral notes, and return value. Every sentence carries useful information, and the most important scoping information is front-loaded.

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 creation tool with no output schema and only negative annotations, the description covers the essential operational aspects: what it creates, how periods are determined, the non-idempotent behavior, the validation workflow, and what the response contains. An agent has enough context to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantic context by explaining the relationship between absencesPeriods and startDate/endDate, including the fallback behavior when absencesPeriods is omitted. This clarifies a subtle interaction that the schema alone does not convey.

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 verb and object: 'Crée une demande d'absence' for a resource, and lists examples (congés, RTT, maladie). It also distinguishes itself from boond_absences_update, so an agent can immediately tell creation apart from modification.

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' section states the exact scenario for using this tool, and 'Plutôt que' explicitly names boond_absences_update as the alternative for modifying an existing request. It also clarifies that validation state is handled elsewhere via boond_validations_search, giving clear 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

Other Tools