Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des avantages

boond_advantages_search
Read-onlyIdempotent

Retrieve employee benefits like meal vouchers, insurance, or bonuses for a given resource ID, since no global advantages endpoint exists.

Instructions

Liste les avantages (tickets restaurant, mutuelle, véhicule, primes...) d'une ressource.

Plutôt que : boond_resources_advantages quand on part d'une ressource précise.

resourceId est obligatoire : l'API n'a pas de recherche globale des avantages (GET /advantages n'existe pas), la liste est servie par GET /resources/{id}/avantages. advantageTypes restreint aux types <reference>_<agencyId>.

Returns: Liste des avantages de la ressource.

  • 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.
pageSizeNoNombre de résultats par page (max: 500, défaut: 30)
resourceIdYesID de la ressource dont on liste les avantages (route /resources/{id}/advantages)
advantageTypesNoTypes d'avantage à conserver, au format `<reference>_<agencyId>` (référence du type + ID d'agence, ex: '2_1').

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. Changed7 schema fields changedv2.17.0
    • addedInput schema / properties / advantageTypes
      Added value: +{
+  "description": "Types d'avantage à conserver, au format `<reference>_<agencyId>` (référence du type + ID d'agence, ex: '2_1').",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / keywords
      Removed value: -{
-  "description": "Mots-clés de recherche",
-  "type": "string"
-}
    • changedInput schema / properties / page / description
      Previous value: -"Numéro de page (max: 100)"New value: +"Numéro de page (défaut: 1, max: 100)"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Résultats par page"New value: +"Nombre de résultats par page (max: 500, défaut: 30)"
    • changedInput schema / properties / resourceId / description
      Previous value: -"Filtrer par ID ressource"New value: +"ID de la ressource dont on liste les avantages (route /resources/{id}/advantages)"
    • addedInput schema / properties / resourceId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / required
      Added value: +[
+  "resourceId"
+]
  3. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. 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"
+}
  5. First observedv2.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: that `fields` is an MCP-side projection never sent to the API, and that exceeding the pagination bounds results in refusal ('au-delà : refus'), which is real operational context.

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 the purpose, then routes, constraints, returns and per-parameter notes. Efficient overall, though the 'Returns:' line largely restates the opening sentence and the alternative-tool sentence is awkwardly constructed.

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?

With no output schema, the description does at least sketch the return (a list of the resource's advantages) and covers the required parameter, projection behavior and pagination bounds. Complete enough to invoke correctly, though the return shape is described only in the vaguest terms.

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 goes slightly beyond the schema by explaining *why* `resourceId` is required (no global endpoint; list is served by GET /resources/{id}/avantages) and by clarifying the `fields` projection's MCP-side nature and the format of `advantageTypes`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (liste) and resource (avantages d'une ressource) and even enumerates concrete examples (tickets restaurant, mutuelle, véhicule, primes), so the agent knows what a 'advantage' is. It attempts sibling differentiation against `boond_resources_advantages`, but the phrasing 'Plutôt que : ... quand on part d'une ressource précise' is ambiguous — that condition appears to describe this tool's own scope, so the routing signal is not fully clean.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names an alternative tool (`boond_resources_advantages`) and the condition that selects it, and warns that no global advantage search exists ('GET /advantages n'existe pas'), which prevents a wasted call. The alternative-selection sentence is worded confusingly, but the when-to-use context is present.

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