Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Modifier un(e) note de frais

boond_expenses_update
Idempotent

Update an existing expense report by ID with partial field updates, leaving unspecified fields unchanged. Replace expense lines entirely when included.

Instructions

Met à jour un(e) note de frais existant(e), identifié(e) par son ID.

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_expenses_create si l'enregistrement n'existe pas encore.

  • Mise à jour partielle : seuls les champs fournis sont écrits, les autres sont laissés en place.

  • Attention aux champs de type tableau, qui sont remplacés et non fusionnés.

Returns : confirmation et fiche mise à jour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de la note de frais à modifier
closedNoClôturer la note de frais
advanceNoAvance à reprendre
actualExpensesNo⚠️ REMPLACE l'intégralité des lignes existantes. Pour ajouter une ligne, relire la note via `boond_expenses_get` et renvoyer l'ensemble des lignes. Omettre pour ne toucher qu'aux autres champs.
currencyAgencyNoID de devise de l'agence
exchangeRateAgencyNoTaux de change agence
informationCommentsNoCommentaires
ratePerKilometerTypeReferenceNoCode du barème kilométrique

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoIdentifiant de l'entité créée/modifiée
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.14.0
    • addedInput schema / properties / actualExpenses
      Added value: +{
+  "description": "⚠️ REMPLACE l'intégralité des lignes existantes. Pour ajouter une ligne, relire la note via `boond_expenses_get` et renvoyer l'ensemble des lignes. Omettre pour ne toucher qu'aux autres champs.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "activityType": {
+        "default": "production",
+        "description": "Type d'activité rattachée au frais.",
+        "enum": [
+          "production",
+          "internal",
+          "absence"
+        ],
+        "type": "string"
+      },
+      "amountIncludingTax": {
+        "description": "Montant TTC. Ignoré pour un frais kilométrique (recalculé = km × barème).",
+        "type": "number"
+      },
+      "batchId": {
+        "description": "ID du lot. Absent = aucun lot.",
+        "type": "string"
+      },
+      "currency": {
+        "default": 0,
+        "description": "ID de devise (`setting.currency`, 0 = EUR).",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "deliveryId": {
+        "description": "ID de la prestation (delivery) à imputer. Obligatoire — voir `boond_expenses_default`.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "exchangeRate": {
+        "default": 1,
+        "description": "Taux de change vers la devise agence.",
+        "type": "number"
+      },
+      "expenseTypeReference": {
+        "description": "Code du type de frais (`reference`), à lire via `boond_expenses_default` — les types de frais sont définis par agence et ne figurent PAS dans `boond_application_dictionary`. À omettre pour un frais kilométrique.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "file": {
+        "description": "ID du justificatif déjà téléversé, suffixé (ex: `52979_proof`). Un fichier doit d'abord être créé via `boond_documents_create` (`parentType: 'expensesReport'`).",
+        "type": "string"
+      },
+      "isKilometricExpense": {
+        "default": false,
+        "description": "`true` pour un frais kilométrique : renseigner `numberOfKilometers` et omettre `expenseTypeReference`.",
+        "type": "boolean"
+      },
+      "numberOfKilometers": {
+        "description": "Nombre de kilomètres (frais kilométrique uniquement).",
+        "type": "number"
+      },
+      "projectId": {
+        "description": "ID du projet à imputer. Obligatoire — les couples (projet, prestation) autorisés sont donnés par `boond_expenses_default`.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "reinvoiced": {
+        "default": false,
+        "description": "Frais refacturable au client.",
+        "type": "boolean"
+      },
+      "startDate": {
+        "description": "Date du frais (YYYY-MM-DD). Doit tomber dans le mois `term` de la note de frais.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "tax": {
+        "description": "Taux de TVA en % (ex: 20 pour 20 %) — un taux, pas un montant. Défaut API: 0.",
+        "type": "number"
+      },
+      "title": {
+        "description": "Description libre de la ligne (marchand, motif, invités...).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "startDate",
+      "projectId",
+      "deliveryId"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / advance
      Added value: +{
+  "description": "Avance à reprendre",
+  "type": "number"
+}
    • removedInput schema / properties / amount
      Removed value: -{
-  "description": "Montant",
-  "type": "number"
-}
    • addedInput schema / properties / closed
      Added value: +{
+  "description": "Clôturer la note de frais",
+  "type": "boolean"
+}
    • addedInput schema / properties / currencyAgency
      Added value: +{
+  "description": "ID de devise de l'agence",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / informationComments
      Added value: +{
+  "description": "Commentaires",
+  "type": "string"
+}
    • removedInput schema / properties / note
      Removed value: -{
-  "description": "Description",
-  "type": "string"
-}
    • addedInput schema / properties / ratePerKilometerTypeReference
      Added value: +{
+  "description": "Code du barème kilométrique",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • removedInput schema / properties / state
      Removed value: -{
-  "description": "État",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • removedInput schema / properties / term
      Removed value: -{
-  "description": "Période de la note de frais (YYYY-MM)",
-  "type": "string"
-}
  2. Changed2 schema fields changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed2 schema fields changedv2.8.0
    • addedInput schema / properties / exchangeRateAgency
      Added value: +{
+  "description": "Taux de change agence",
+  "type": "number"
+}
    • addedInput schema / properties / term
      Added value: +{
+  "description": "Période de la note de frais (YYYY-MM)",
+  "type": "string"
+}
  4. Changed1 schema field changedv2.7.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Identifiant de l'entité créée/modifiée",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. First observedv2.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds crucial behavioral context: partial update (only provided fields are written), array fields are replaced not merged, and the return includes confirmation and the updated record. This goes beyond annotations without contradicting them.

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 concise and well-structured. It front-loads the purpose, then provides usage guidance, then key behavioral notes. Each sentence earns its place without redundancy.

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?

The description is complete for an update tool: it explains partial update semantics, warns about array replacement, refers to related tools (`boond_expenses_get`, `boond_expenses_default`, `boond_documents_create`) for necessary prerequisites, and mentions the output. Given the output schema is present and the schema documents parameters thoroughly, nothing critical is missing.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage of parameters with detailed descriptions, so the description itself doesn't add much beyond what the schema already says. The description highlights the array replacement behavior for `actualExpenses`, which is valuable additional semantics not fully captured in the schema. However, most parameter meaning is already in the schema, so the added value is moderate.

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 the tool updates an existing expense report identified by its ID, distinguishing it from `boond_expenses_create`. It specifies the resource (note de frais) and the action (met à jour), which is 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 explicitly says when to use this tool (to modify a few fields of an already existing record) and when not to (use `boond_expenses_create` if the record doesn't exist yet). It also clarifies partial update semantics and warns about array replacement, which is essential for correct usage.

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