Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Alertes du tableau de bord

boond_alerts_search
Read-onlyIdempotent

List configured alert indicators and thresholds to know what to monitor for contract endings, probation, unvalidated reports, and upcoming actions.

Instructions

Liste les indicateurs d'alerte configurés sur le tableau de bord de l'utilisateur (fins de contrat, périodes d'essai, CRA / notes / absences non validés, actions à venir…) avec leurs seuils : période en jours, états visés, périmètre.

Quand : en premier, pour « qu'est-ce qui demande mon attention aujourd'hui ? » — la liste dit quoi surveiller et avec quels seuils ; l'outil *_search du module donne les éléments. Plutôt que : la ressource boond://alerts/me (même contenu en JSON) ; le prompt attention_du_jour enchaîne indicateur → recherche.

  • GET /alerts renvoie la configuration des indicateurs, pas des occurrences (vérifié le 2026-09-26) : une ligne par indicateur, params.period en jours (-1 = mois précédent), X / Y = IDs d'états ou de types, perimeter (dynamic_data = mes données). Aucun filtre, aucune pagination, pas de /alerts/{id}.

  • Correspondances : contractsEndedUpcoming → boond_contracts_search period: "ending" ; resourcesProbationaryDateUpcoming → period: "probationEnding" ; timesReportsWithNoValidation / expensesReportsWithNoValidation / absencesReportsWithNoValidation → boond_validations_search (documentTypes, waitingForValidation) ; actionsUpcoming → boond_actions_search period: "started".

Returns : une ligne par indicateur (module, indicator, paramètres, cadence de rapport) et structuredContent.items[]. Lecture seule.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoProjection : attributs ou relations (type#id) par résultat (ex: ['title','dependsOn']). Absent = résumé standard. Noms inconnus ignorés.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNombre d'éléments retournés sur cette page
itemsYes
totalNoNombre total de résultats côté BoondManager

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. Addedv2.17.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantial context: no filters, no pagination, no `/alerts/{id}` endpoint, exact `params.period` semantics (`-1` = previous month), and X/Y meaning. This goes well beyond what the annotations declare.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then When/Rather-than, then API details — good ordering. It is dense and long, but nearly every sentence (endpoint behavior, param encoding, indicator-to-tool mapping) earns its place; a little trimming of the verification date and parenthetical asides would help.

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?

With output schema and annotations both present, the description does not need to restate return values, yet it still notes the per-indicator row shape and read-only nature. Combined with endpoint constraints and sibling routing, an agent has everything needed to call 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 already 100% for the single `fields` param, so the baseline is 3. The description adds value beyond the schema by explaining that the projection is MCP-side and never sent to the API, and that it replaces the standard summary — genuinely useful operational detail.

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 and resource (list dashboard alert indicators) and explicitly contrasts it with the sibling `*_search` tools by clarifying this returns CONFIGURATION, not occurrences. An agent can distinguish it from any of the many sibling search tools without opening a 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 explicit 'Quand' (use first for 'what needs my attention today?') and 'Plutôt que' sections naming the alternative resource `boond://alerts/me` and the prompt `attention_du_jour`. Also maps each indicator to the sibling tool that resolves it, which is unusually actionable 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