boondmanager-mcp-server

Rechercher des logs

boond_logs_search

Read-onlyIdempotent

Search audit logs to trace who modified what and when, returning a list of user actions with filtering and pagination options.

Instructions

Recherche des logs d'audit dans BoondManager (historique des actions utilisateurs).

Quand : pour retracer qui a modifié quoi et quand. Plutôt que : le _get du domaine concerné (boond_candidates_get, boond_projects_get…) pour l'état actuel d'un enregistrement : celui-ci ne renvoie que l'historique des modifications.

Returns: Liste des logs correspondants.

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.
Pagination : pageSize 1–500 (défaut 30), page 1–100 — au-delà : refus, affiner les filtres.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Numéro de page (défaut: 1, max: 100)
`fields`	No	Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
`keywords`	No	Mots-clés de recherche (nom, email, compétences...)
`pageSize`	No	Nombre de résultats par page (max: 500, défaut: 30)

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Nombre d'éléments retournés sur cette page
`items`	Yes
`total`	No	Nombre total de résultats côté BoondManager

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.12.2Aug 14, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedv2.9.0Aug 3, 2026

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"
+}

Changed1 schema field changedv2.7.0Jun 19, 2026

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"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses meaningful behavior: `fields` is a MCP-side projection never sent to the API, unknown names are ignored, it replaces the summary on large pages, and pagination beyond `pageSize` 500 or `page` 100 is refused. These details help an agent predict and debug behavior.

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?

The definition is compact and well-structured: purpose first, then when/alternative, then bullets for field projection and pagination. It loses one point due to the slightly ambiguous 'celui-ci ne renvoie que l'historique' sentence and the mildly redundant 'Returns: Liste des logs correspondants.' Overall still efficient and scannable.

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 the rich annotations, a 100%-covered input schema, and the presence of an output schema, the description is complete enough for an agent to invoke the tool correctly. It covers usage context, alternatives, field projection behavior, and pagination limits without needing to explain return structure.

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 schema already documents all parameters. The description adds extra non-obvious meaning for `fields` (MCP-side only, never sent to API, use on big pages) and for pagination (out-of-range requests are refused). It does not add much beyond the schema for `keywords`, but it compensates enough to exceed the baseline of 3.

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 verb and resource: 'Recherche des logs d'audit dans BoondManager (historique des actions utilisateurs).' It clearly scopes the tool to audit logs and user-action history, and it distinguishes itself from domain `_get` tools like `boond_candidates_get` and `boond_projects_get`, which return current record state.

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' section explicitly states when to use this tool: 'pour retracer qui a modifié quoi et quand.' The 'Plutôt que' section names the alternatives (`_get` on the domain concerned) and the condition for choosing them instead, which is current record state. This is explicit and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server