Skip to main content
Glama

mb-mastering

by com.mathieuberthet
OverviewDiscussionsAdmin

prepare_quote_email

RÉSERVÉ AU STUDIO (token d'administration requis). Prépare un brouillon — ou envoie — l'email d'un devis ou d'une facture PDF à un client, depuis contact@mathieuberthet.com. Par défaut (mode « draft »), l'email est déposé dans les Brouillons du webmail OVH pour relecture avant envoi ; en mode « send », il est envoyé immédiatement puis archivé dans Envoyés. Le PDF est récupéré par le serveur directement dans Qonto (qonto_type + qonto_number) — ou fourni en base64 pour un document externe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoAdresses en copie (string CSV ou array).
modeNodraft (défaut) : brouillon dans le webmail OVH. send : envoi immédiat.
subjectNoSujet de l'email. Défaut : « MB Mastering — Devis/Facture n° … ».
qonto_idNoId Qonto du document (alternative à qonto_number).
auth_tokenNoToken d'administration (si le client MCP ne permet pas le header Authorization).
pdf_base64NoPDF externe encodé en base64 — seulement si le document n'est pas dans Qonto.
qonto_typeNoRECOMMANDÉ : le serveur va chercher le PDF dans Qonto lui-même (aucun base64 à transporter). quote = devis, invoice = facture.
referencesNoChaîne References (Message-IDs séparés par espaces). Auto = in_reply_to si absent.
client_nameNoNom du client (salutation et en-tête To).
in_reply_toNoMessage-ID du mail auquel on répond (avec ou sans chevrons), pour threading IMAP/Gmail.
body_messageNoParagraphe personnalisé inséré dans le corps par défaut.
client_emailYesAdresse email du client destinataire.
pdf_filenameNoNom du fichier joint. Défaut : Devis-<n>.pdf / Facture-<n>.pdf.
qonto_numberNoNuméro Qonto du document (D-2026-003, F-2026-001). Défaut : document_number.
document_typeYesType de document joint.
document_numberYesNuméro du document, ex. 202608-2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / pdf_base64 / description
      Previous value: -"Contenu du PDF du document, encodé en base64."New value: +"PDF externe encodé en base64 — seulement si le document n'est pas dans Qonto."
    • addedInput schema / properties / qonto_id
      Added value: +{
+  "description": "Id Qonto du document (alternative à qonto_number).",
+  "type": "string"
+}
    • addedInput schema / properties / qonto_number
      Added value: +{
+  "description": "Numéro Qonto du document (D-2026-003, F-2026-001). Défaut : document_number.",
+  "type": "string"
+}
    • addedInput schema / properties / qonto_type
      Added value: +{
+  "description": "RECOMMANDÉ : le serveur va chercher le PDF dans Qonto lui-même (aucun base64 à transporter). quote = devis, invoice = facture.",
+  "enum": [
+    "quote",
+    "invoice"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "document_type",
-  "document_number",
-  "client_email",
-  "pdf_base64"
-]New value: +[
+  "document_type",
+  "document_number",
+  "client_email"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / cc
      Added value: +{
+  "description": "Adresses en copie (string CSV ou array).",
+  "type": [
+    "string",
+    "array"
+  ]
+}
    • addedInput schema / properties / in_reply_to
      Added value: +{
+  "description": "Message-ID du mail auquel on répond (avec ou sans chevrons), pour threading IMAP/Gmail.",
+  "type": "string"
+}
    • addedInput schema / properties / references
      Added value: +{
+  "description": "Chaîne References (Message-IDs séparés par espaces). Auto = in_reply_to si absent.",
+  "type": "string"
+}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It details the default draft mode (stored in OVH webmail Drafts), send mode (immediate send and archive in Sent), the requirement of an admin token, and how the PDF is sourced/retrieved. This is thorough and surfaces side effects and constraints upfront.

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 text is a compact two-sentence block that front-loads the access restriction, clearly states the action and mode distinction, and ends with the PDF sourcing logic. Every sentence carries essential information without fluff.

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?

Given the tool's complexity (16 parameters, no output schema), the description covers the core semantics: intended purpose, modes, sender identity, and PDF handling. It doesn't explain return values or failure behavior, but the detailed parameter descriptions in the schema compensate; an agent has enough context to invoke the tool correctly.

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 each parameter is already documented. The description adds value by connecting qonto_type + qonto_number to the server-side PDF retrieval and pdf_base64 to external documents, clarifying the parameter relationships beyond individual schema entries. It doesn't duplicate every parameter, which keeps it focused.

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 uses specific verbs ('Prépare un brouillon — ou envoie') and names the resource ('email d'un devis ou d'une facture PDF à un client'), clearly distinguishing this emailing/PDF tool from document-management siblings like qonto_create_quote. It also states the sending address and the two PDF sources, leaving no doubt about the tool's role.

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

Usage Guidelines4/5

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

It gives clear context for use: restricted to the studio, admin token required, draft mode by default vs immediate send mode, and the PDF retrieval options (Qonto or base64). It doesn't explicitly name alternatives or state when not to use it, but the context is strong enough for an agent to infer the correct situation.

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

All mb-mastering toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources