boondmanager-mcp-server

Rechercher des agences

boond_agencies_search

Read-onlyIdempotent

Search and list BoondManager agencies by keywords to find agency IDs by name or enumerate all agencies. Returns read-only summaries with ID and label, plus total count.

Instructions

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

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

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

Name	Required	Description
`page`	No	Numéro de page (défaut: 1, max: 100)
`fields`	No	Projection : attributs ou relations (type#id) par résultat (ex: ['title','dependsOn']). 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.

Changed1 schema field changedv2.18.0Oct 2, 2026

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

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.9/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent, so the safety profile is covered; the description goes well beyond by disclosing that pageSize and page are silently IGNORED by the API (the route always returns the full table), that the usual result is a one-line summary, and that structuredContent.total reports the server-side count. This is exactly the behavioral context an agent cannot get from annotations or schema, and it prevents wasted pagination calls.

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/Alternative/Returns, then per-parameter bullets — well structured and largely waste-free. Slightly verbose in places (the fields bullet partly restates the schema's own description), but every sentence adds actionable information.

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?

Output schema exists, so return shape needn't be explained, yet the description still clarifies that each row is an ID + main label and that structuredContent.total is the BoondManager-side count. Combined with the pagination caveat and projection semantics, an agent has everything needed to call this correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 decisive semantics the schema omits: `fields` is an MCP-side projection never sent to the API, unknown names are ignored, and it should be used on large pages. It also neutralizes `page`/`pageSize`, whose schema defaults would otherwise mislead the agent into paginating a non-paginated endpoint.

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 agences de BoondManager') and immediately differentiates from the sibling boond_agencies_get by noting the search only returns a one-line summary per agency. An agent can distinguish this from the many other *_search siblings and from the corresponding _get 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?

Explicit 'Quand' clause gives two concrete triggers (retrieve an agency ID from its name, or enumerate existing agencies), and a 'Plutôt que' clause names the alternative (boond_agencies_get) and the condition that selects it (ID already known). No inference required.

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

Deploy Server