Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des demandes d'absence

boond_absences_search
Read-onlyIdempotent

Search absence requests in BoondManager and retrieve their validation status. Filter by resource, month range, or keywords to locate specific leave records.

Instructions

Recherche des demandes d'absence dans BoondManager.

Quand : pour retrouver des demandes d'absence et leur état de validation. Plutôt que : boond_planning_absences_search pour la vue calendaire (qui est absent quand), et boond_validations_search pour ce qui reste en attente de validation.

Args:

  • keywords (string, optional): Termes de recherche. resourceId est converti en COMP.

  • startMonth, endMonth (string, optional): Periode au format YYYY-MM.

  • page, pageSize: Pagination

Returns: Liste des demandes d'absence correspondantes.

  • 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNuméro de page (max: 100)
fieldsNoProjection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
endMonthNoMois de fin de période (YYYY-MM)
keywordsNoMots-clés de recherche
pageSizeNoRésultats par page
resourceIdNoFiltrer par ID ressource
startMonthNoMois de début de période (YYYY-MM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv2.9.0
    • 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"
+}
  3. Changed4 schema fields changedv2.8.0
    • removedInput schema / properties / endDate
      Removed value: -{
-  "description": "Date de fin de période (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / endMonth
      Added value: +{
+  "description": "Mois de fin de période (YYYY-MM)",
+  "type": "string"
+}
    • removedInput schema / properties / startDate
      Removed value: -{
-  "description": "Date de début de période (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / startMonth
      Added value: +{
+  "description": "Mois de début de période (YYYY-MM)",
+  "type": "string"
+}
  4. First observedv2.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavior beyond that: the 'fields' projection is local-only and never sent to the API, unknown field names are ignored, and resourceId is normalized to COMP<id>. It does not detail pagination behavior, but the annotation coverage lowers the burden.

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, alternatives, arguments, return value, and a focused note on the 'fields' projection. It is compact, front-loaded, and contains no filler while still covering the most decision-relevant details.

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?

For a read-only search tool with 100% schema coverage and safety annotations, the description is largely complete: it explains purpose, alternatives, period format, pagination, and the special 'fields' behavior. Since there is no output schema, the return description is somewhat minimal ('Liste des demandes d'absence correspondantes'), but it is still enough for basic 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 baseline is 3. The description adds extra meaning by explaining the resourceId-to-COMP<id> conversion and detailing the 'fields' projection behavior (local, replaces summary, unknown names ignored), which goes beyond the schema's short 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 opens with a specific action and resource: 'Recherche des demandes d'absence dans BoondManager' and states what information is retrievable ('leur état de validation'). It also explicitly names sibling alternatives, so the tool is clearly distinguished from planning_absences_search and validations_search.

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' and 'Plutôt que' sections give explicit usage context and name the alternatives: use this for absence requests and their validation state, planning_absences_search for the calendar view, and validations_search for items pending validation. This leaves no ambiguity about when to select this tool.

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