Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Modifier une absence

boond_absences_update
Idempotent

Update an existing absence request by ID to correct dates, reason, or comment. Only provided fields change; absence periods are fully replaced.

Instructions

Met à jour une demande d'absence existante, identifiée par son ID.

Quand : pour corriger les dates, le motif ou le commentaire d'une demande déjà déposée. Plutôt que : boond_absences_create si la demande n'existe pas encore.

  • Mise à jour partielle : seuls les champs fournis sont écrits.

  • absencesPeriods fait exception — le tableau fourni remplace l'intégralité des périodes existantes.

Returns : confirmation et fiche mise à jour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de l'absence à modifier
noteNoCommentaire / motif
endDateNoDate de fin (YYYY-MM-DD)
startDateNoDate de début (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.17.0
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • addedInput schema / properties / id / pattern
      Added value: +"^\\d+$"
    • removedInput schema / properties / state
      Removed value: -{
-  "description": "État de la demande",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
  2. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv2.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With annotations already covering read-only/idempotency, the description adds real behavioral value: partial update semantics and the exception that absencesPeriods replaces all existing periods. However, absencesPeriods is not present in the input schema and is disallowed by additionalProperties:false, which slightly undermines the disclosure.

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 compact, front-loaded with the core action, and uses short labeled sections plus two focused bullets. No sentence is wasted.

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?

Given no output schema, describing the return as confirmation plus updated record is helpful. The tool is nearly complete, but the reference to absencesPeriods creates a schema/description mismatch that an agent would have to resolve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the parameters. The description adds a useful partial-update note, but its mention of absencesPeriods is confusing because that field cannot be provided via this schema, so it does not clearly improve parameter understanding.

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 'Met à jour une demande d'absence existante, identifiée par son ID', giving a precise verb, resource, and identifier-based scope. This is clearly distinct from the sibling boond_absences_create, which creates rather than updates.

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 explicitly states when to use the tool ('pour corriger les dates, le motif ou le commentaire d'une demande déjà déposée') and names the alternative, boond_absences_create, with the condition that selects it (absence doesn't exist yet).

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