Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des factures fournisseur

boond_provider_invoices_search
Read-onlyIdempotent

Search and list supplier invoices by provider, status, or period. Returns read-only summaries with reference, date, and amounts, with optional field projection and pagination.

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 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
pageNoNumero de page (max: 100)
fieldsNoProjection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
keywordsNoMots-cles de recherche
pageSizeNoResultats par page
companyIdNoFiltrer par ID societe fournisseur
resourceIdNoFiltrer par ID ressource via mot-cle COMP<id>

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. 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"
+}
  3. Changed5 schema fields changedv2.8.0
    • 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"
+}
  4. First observedv2.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds non-annotation details: the fields parameter is an MCP-side projection never transmitted to the API, unknown field names are ignored, and pagination limits (pageSize 1–500, page 1–100). These are useful behaviors beyond what annotations cover, though the description could mention the read-only nature again but that's redundant.

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 description is structured with clear labels (Quand, Plutôt que, Returns, and bullet points for fields and pagination). It's front-loaded with the core purpose and use case. Some detail on fields could be condensed, but it remains efficient and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main intent, return type (page of summaries), and pagination, but promises use cases 'par fournisseur, état ou période' without explicit parameters for state or period—only companyId is clear for supplier filtering. This gap may confuse an agent on how to filter by status or period. Given no output schema, the description also doesn't detail the summary fields beyond reference, date, and amounts, but that's acceptable.

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% (all parameters described in the schema), so baseline is 3. The description goes beyond by explaining the fields parameter's MCP-side behavior and pagination constraints, which helps an agent understand how to use them effectively. This adds enough value to warrant a 4.

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 clearly states it lists and searches supplier invoices (factures reçues des prestataires), and explicitly differentiates from boond_invoices_search for sales invoices. The verb 'Liste et recherche' and the resource 'factures fournisseur' make the purpose unambiguous.

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 description includes 'Quand' (when to use) explaining it's for tracking purchase invoices by supplier, status, or period, and 'Plutôt que' (rather than) explicitly naming boond_invoices_search as the alternative for sales invoices. This provides clear guidance on selection among siblings.

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