Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher le planning des absences

boond_planning_absences_search
Read-onlyIdempotent

Search the absence planning calendar in BoondManager to see who is absent over a given period, using keywords and pagination filters.

Instructions

Recherche le planning des absences dans BoondManager (vue globale des absences prévues).

Quand : pour savoir qui est absent sur une période — une vue calendaire, pas un suivi de demandes. Plutôt que : boond_absences_search pour les demandes elles-mêmes (motif, état de validation, demandeur), que cette vue ne détaille pas.

Returns: Planning des absences.

  • fields : projection côté MCP, jamais transmise à l'API — remplace le résumé par les seuls attributs/relations 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
NameRequiredDescriptionDefault
pageNoNuméro de page (défaut: 1, max: 100)
fieldsNoProjection : attributs ou relations (type#id) par résultat (ex: ['title','dependsOn']). Absent = résumé standard. Noms inconnus ignorés.
keywordsNoMots-clés de recherche (nom, email, compétences...)
pageSizeNoNombre de résultats par page (max: 500, défaut: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.18.0
    • changedInput schema / properties / fields / description
      Previous value: -"Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés."New value: +"Projection : attributs ou relations (type#id) par résultat (ex: ['title','dependsOn']). Absent = résumé standard. Noms inconnus ignorés."
  2. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. 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"
+}
  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 readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: `fields` is an MCP-side projection never transmitted to the API, and pagination caps (pageSize 1–500, page 1–100) result in refusal beyond the limits, prompting filter refinement.

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?

Front-loaded purpose, then 'Quand'/'Plutôt que' routing, then Returns, then two tight bullets for projection and pagination. Every sentence carries routing or behavioral information with no filler.

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 with no output schema, the description covers routing, projection semantics, and pagination limits well. The only soft spot is 'Returns: Planning des absences', which is a near-restatement of the title rather than a description of the returned shape.

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 baseline is 3, but the description adds meaning the schema lacks: `fields` replaces the standard summary with only listed attributes/relations, unknown names are ignored, and it is recommended for large pages. Pagination bounds and their refusal behavior are also restated with intent.

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?

States a specific verb ('Recherche') plus resource ('planning des absences') and scope ('vue globale des absences prévues'). It explicitly contrasts itself with `boond_absences_search`, so an agent can distinguish the two without opening either schema.

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?

Has an explicit 'Quand' clause (who is absent over a period, a calendar view, not request tracking) and a 'Plutôt que' clause naming the alternative `boond_absences_search` and the exact fields (motif, état de validation, demandeur) it does not detail.

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