Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des achats/sous-traitance

boond_purchases_search
Read-onlyIdempotent

Find purchase orders and subcontracting commitments in BoondManager, filtering by company or project. Use to track expense commitments before supplier invoices arrive.

Instructions

Recherche des achats et sous-traitances dans BoondManager, avec filtres par société et projet.

Quand : pour suivre les engagements de dépense et la sous-traitance. Plutôt que : boond_provider_invoices_search pour les factures effectivement reçues : l'achat est l'engagement, la facture fournisseur le document qui le solde.

companyId / projectId sont convertis en références keywords (CSOC / PRJ) : l'API n'a pas de paramètre dédié.

Returns: Liste des achats 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
NameRequiredDescriptionDefault
pageNoNuméro de page (défaut: 1, max: 100)
fieldsNoProjection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
keywordsNoMots-clés de recherche
pageSizeNoNombre de résultats par page (max: 500, défaut: 30)
companyIdNoFiltrer par ID société (référence keywords CSOC<id>)
projectIdNoFiltrer par ID projet (référence keywords PRJ<id>)

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. Changed7 schema fields changedv2.17.0
    • changedInput schema / properties / companyId / description
      Previous value: -"Filtrer par ID société"New value: +"Filtrer par ID société (référence keywords CSOC<id>)"
    • addedInput schema / properties / companyId / pattern
      Added value: +"^\\d+$"
    • 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 / projectId / description
      Previous value: -"Filtrer par ID projet"New value: +"Filtrer par ID projet (référence keywords PRJ<id>)"
    • addedInput schema / properties / projectId / pattern
      Added value: +"^\\d+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "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"
+}
  2. Changed1 schema field changedv2.12.2
    • removedInput 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. First observedv2.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses real behavioral details: companyId/projectId are converted into keyword references (CSOC<id>/PRJ<id>) because the API has no dedicated parameters, fields is an MCP-side projection never sent to the API, and pagination is bounded with clear refusal behavior. No contradiction with annotations.

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

Conciseness5/5

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

The description is dense but organized: purpose first, then when/alternative, then internal behavior, then return, then parameter-specific notes. Every sentence earns its place and there is no filler.

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 input schema and output schema, the description covers what, when, the key alternative, important API translation behavior, return value, and pagination limits. An agent has enough to call this tool correctly without guessing.

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?

Even though schema coverage is 100%, the description adds substantial meaning: it explains the keyword conversion for companyId/projectId, the MCP-side behavior of fields, and the exact pagination constraints. This goes well beyond the schema's field-level descriptions.

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 ('Recherche des achats et sous-traitances dans BoondManager') and the main filters. It explicitly contrasts itself with boond_provider_invoices_search, which helps an agent distinguish search purchases from search provider invoices 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?

Provides an explicit 'Quand' condition ('pour suivre les engagements de dépense et la sous-traitance') and a clear alternative ('Plutôt que : boond_provider_invoices_search...'). This is concrete, actionable guidance about when to choose this tool over its closest sibling.

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