boondmanager-mcp-server

Rechercher des factures fournisseur

boond_provider_invoices_search

Read-onlyIdempotent

Search and list supplier invoices by supplier, status, or period to track purchase invoices. Returns read-only summaries with reference, date, and amounts.

Instructions

Liste et recherche les factures fournisseur (factures reçues des prestataires).

Quand : pour suivre les factures d'achat, par fournisseur, état ou période. Plutôt que : boond_invoices_search pour les factures de vente adressées aux clients — sens opposé, endpoint distinct.

Returns : page de résumés de factures fournisseur (référence, date, montants). 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 : 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 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
`pageSize`	No	Nombre de résultats par page (max: 500, défaut: 30)
`companyId`	No	Filtrer par ID société fournisseur (référence keywords CSOC<id>)
`resourceId`	No	Filtrer par ID ressource (référence keywords COMP<id>)

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

Changed8 schema fields changedv2.17.0Sep 26, 2026

changedInput schema / properties / companyId / description

Previous value: -"Filtrer par ID societe fournisseur"New value: +"Filtrer par ID société fournisseur (référence keywords CSOC<id>)"

addedInput schema / properties / companyId / pattern
```
Added value: +"^\\d+$"
```

changedInput schema / properties / keywords / description

Previous value: -"Mots-cles de recherche"New value: +"Mots-clés de recherche"

changedInput schema / properties / page / description

Previous value: -"Numero de page (max: 100)"New value: +"Numéro de page (défaut: 1, max: 100)"

changedInput schema / properties / pageSize / description

Previous value: -"Resultats 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 via mot-cle COMP<id>"New value: +"Filtrer par ID ressource (référence keywords COMP<id>)"

addedInput schema / properties / resourceId / 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"
+}

Changed1 schema field changedv2.12.2Aug 14, 2026
- removedInput 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"
+}

Changed5 schema fields changedv2.8.0Jun 29, 2026

changedInput schema / properties / companyId / description

Previous value: -"Filtrer par ID société fournisseur"New value: +"Filtrer par ID societe fournisseur"

changedInput schema / properties / keywords / description

Previous value: -"Mots-clés de recherche"New value: +"Mots-cles de recherche"

changedInput schema / properties / page / description

Previous value: -"Numéro de page (max: 100)"New value: +"Numero de page (max: 100)"

changedInput schema / properties / pageSize / description

Previous value: -"Résultats par page"New value: +"Resultats par page"

addedInput schema / properties / resourceId

Added value: +{
+  "description": "Filtrer par ID ressource via mot-cle COMP<id>",
+  "type": "string"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, and 'Lecture seule' merely repeats that. However, the description adds meaningful context beyond annotations: the pagination limits with the explicit refusal beyond them, and that the fields projection is MCP-side and never transmitted to the API.

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?

Front-loads the definition, then uses labeled sections (Quand, Plutôt que, Returns) followed by two focused bullets. Every sentence carries information; no filler or repetition.

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 six optional parameters, rich annotations and an output schema, the description supplies everything needed: purpose, when to use versus the sibling, return summary, pagination limits and projection behavior. No critical gap remains.

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, but the description adds useful context for the fields parameter (MCP-side projection, never sent to the API, best for large pages). It also states the pagination bounds and refusal behavior, adding meaning beyond the schema's min/max.

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 specific verb+resource ('Liste et recherche les factures fournisseur') and defines the resource parenthetically ('factures reçues des prestataires'). Explicitly distinguishes itself from the sibling boond_invoices_search by opposite direction and distinct endpoint.

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?

Contains an explicit 'Quand' clause with concrete tracking scenarios (par fournisseur, état ou période) and a 'Plutôt que' clause naming the alternative tool and the condition under which that alternative applies. Nothing requires inference.

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

Deploy Server