Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des calendriers

boond_calendars_search
Read-onlyIdempotent

Find a BoondManager calendar's ID by name or list all calendars with keyword search.

Instructions

Liste et recherche les calendriers de BoondManager, par mots-clés et pagination.

Quand : pour retrouver l'ID d'un(e) calendrier à partir de son nom, ou pour énumérer les calendriers existant(e)s. Plutôt que : boond_calendars_get si l'ID est déjà connu — la recherche ne renvoie qu'un résumé d'une ligne par calendrier.

Returns : page de résumés (ID + libellé principal), plus structuredContent.total = nombre total côté BoondManager. 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.

  • Pagination sans effet : cette route renvoie toujours la table complète, pageSize et page sont ignorés par l'API — inutile de paginer, tout est déjà là.

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)

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. Changed2 schema fields changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput 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. Changed1 schema field changedv2.7.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Nombre d'éléments retournés sur cette page",
+      "type": "number"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attributes": {
+            "additionalProperties": {},
+            "description": "Attributs projetés (présent si `fields` est fourni)",
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "description": "Résumé standard (absent si `fields` est fourni)",
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Nombre total de résultats côté BoondManager",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "items"
+  ],
+  "type": "object"
+}
  5. First observedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds substantive behavior beyond them: results are one-line summaries, `fields` is an MCP-side projection never sent to the API, and — critically — `page`/`pageSize` are silently ignored by the underlying route so pagination is pointless.

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 and sectioned with 'Quand :', 'Plutôt que :', 'Returns :' and bullets; nearly every sentence earns its place. Minor deduction for the opening line advertising 'pagination' as a capability that the body then states is ineffective, which is slightly self-cancelling.

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?

Given four optional parameters, full annotation coverage, an existing output schema and the summary's description of the returned page shape plus `structuredContent.total`, an agent has everything needed to call this correctly, including the pagination caveat.

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 the baseline is 3, but the description goes further: it explains what `fields` does (replaces the default summary, unknown names ignored, MCP-side only) and discloses that `page`/`pageSize` are no-ops despite being fully described in the schema as functional. That is real meaning added on top of the schema.

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 ('Liste et recherche les calendriers de BoondManager') plus the search scope ('par mots-clés'). It is clearly distinguishable from the sibling `boond_calendars_get`, which is named as the ID-based alternative.

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 :' clause gives concrete triggers (retrieve an ID from a name, enumerate calendars) and the 'Plutôt que :' clause explicitly names the alternative to use when the ID is already known. Both when-to-use and when-not-to-use are covered.

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