Skip to main content
Glama
Mqrtingaler

voxfactura-mcp

by Mqrtingaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

creer_devis_brouillon

Create a draft quote for a client and project with item lines, VAT, validity, and execution time; the quote stays unsent until reviewed in VoxFactura.

Instructions

Crée un devis en BROUILLON (permission devis:write). client_id et chantier_id sont les numéros du client et du chantier dans le compte. Chaque ligne : {designation, quantite, unite, prix_unitaire_ht, taux_tva}, plus en option prestation_id (numéro de la prestation du catalogue) et nature (« bien » pour une vente, « service » sinon ; omise, elle suit la prestation du catalogue puis le réglage du compte). validite_jours : durée de validité (omis = celle réglée sur le compte, 30 jours par défaut). delai_execution : délai imprimé sur le devis (ex. « 3 semaines après acceptation »). Le devis n'est jamais envoyé automatiquement : l'artisan le relit et l'envoie dans VoxFactura. Son numero est nul tant qu'il est brouillon : le numéro définitif lui est attribué à l'envoi.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
objetNo
lignesYes
client_idYes
chantier_idNo
validite_joursNo
delai_executionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / delai_execution
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Delai Execution"
+}
    • addedInput schema / properties / notes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Notes"
+}
    • addedInput schema / properties / validite_jours
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Validite Jours"
+}
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses the required write permission, draft-only status, non-automatic sending, numbering behavior ('numero' null until sent), and default inheritance for optional fields.

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 front-loaded with the core action and every sentence adds substantive detail about defaults, line structure, or lifecycle. It is slightly long, but the density is justified by the creation complexity.

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

Completeness4/5

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

For a 7-parameter create tool with no annotations or output schema, it supplies key defaults, permission requirements, and draft/numbering semantics. It is not fully complete because 'notes' and 'objet' are never explained and no return shape is described.

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 0%, so the description must compensate. It documents client_id, chantier_id, the nested 'lignes' item fields, validite_jours defaults, and delai_execution, but it leaves 'notes' and 'objet' completely undocumented.

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 opens with a specific verb and resource: 'Crée un devis en BROUILLON'. It also states the required permission (devis:write), making the action unambiguous and distinguishable from facture-oriented siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when to use the tool by describing the draft workflow and that the quote is never sent automatically, but it does not explicitly contrast this with alternatives or provide clear when-not-to-use conditions.

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