Skip to main content
Glama

RFQdecoder

by io.github.Mounirt879
OverviewDiscussionsAdmin

Check a supplier quote

verifier_devis

Use this when the user has a supplier quote for a part and wants to know if the price is fair. Compares the quoted price with the price rebuilt from the drawing, line by line, and lists the questions to ask the supplier. Requires a plan_id and the quoted unit price. 1 credit. The quote can be passed either as its unit price (devis.prix_unitaire_eur) or as the PDF file (devis.pdf_base64); with the PDF, the price, quantity and supplier are read automatically and returned in devis_lu.

Input Schema

NameRequiredDescriptionDefault
devisYesSupplier quote: give prix_unitaire_eur, or pdf_base64, or both (prix_unitaire_eur then wins).
matiereYesEx. aluminium, acier, inox, fonte, pa6
plan_idYesIdentifiant rendu par POST /plans
quantiteYes
ajustementsNoParamètres du modèle (voir ajustements_possibles dans la réponse)
epaisseur_mmNoPour la tôle si le plan ne la porte pas
nb_campagnesNo
lot_de_fabricationNoNombre de pièces par lot, ou « commande_entiere »

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / devis / anyOf
      Added value: +[
+  {
+    "required": [
+      "prix_unitaire_eur"
+    ]
+  },
+  {
+    "required": [
+      "pdf_base64"
+    ]
+  }
+]
    • addedInput schema / properties / devis / description
      Added value: +"Supplier quote: give prix_unitaire_eur, or pdf_base64, or both (prix_unitaire_eur then wins)."
    • addedInput schema / properties / devis / properties / pdf_base64
      Added value: +{
+  "contentEncoding": "base64",
+  "contentMediaType": "application/pdf",
+  "description": "Optional: the supplier quote itself as a PDF, base64-encoded (max 8 MB). If prix_unitaire_eur is not given, the unit price is read from this PDF. Text PDFs only (scanned quotes cannot be read: then ask the user for the unit price).",
+  "type": "string"
+}
    • addedInput schema / properties / devis / properties / prix_unitaire_eur / description
      Added value: +"Quoted unit price, EUR excl. VAT."
    • changedInput schema / properties / devis / required
      Previous value: -[
-  "prix_unitaire_eur"
-]New value: +[]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description explains why: '1 credit' is consumed per call, which is meaningful cost/disclosure context. It also discloses a real operational limit (scanned PDFs cannot be read, ask the user for the unit price) and that price/quantity/supplier are auto-extracted and returned in devis_lu. Error modes and refund behavior remain unstated.

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?

Front-loaded with the when-to-use clause, then the operation, then cost, then the input alternatives. Four sentences, all serving a purpose, though the final sentence on the PDF path is dense and could be tightened.

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?

There is no output schema, yet the description indicates what comes back (line-by-line comparison, supplier questions, devis_lu extraction), covering the main return expectations. Given the nested devis object and 8 parameters, it could say more about the model-tuning parameters, but nothing essential for a correct call is missing.

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?

With 75% schema coverage the baseline is 3, but the description adds real clarity on the awkwardly expressed devis object: the quote may be passed as prix_unitaire_eur or pdf_base64, and the precedence rule when both are given. It also names plan_id as required, though it omits that matiere and quantite are also mandatory and says nothing about ajustements, epaisseur_mm, nb_campagnes or lot_de_fabrication.

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 a specific verb and resource ('check a supplier quote') and clarifies the exact operation: comparing the quoted price against the price rebuilt from the drawing, line by line, then listing questions for the supplier. This clearly separates it from sibling pricing tools like chiffrer_piece, which compute rather than verify a price.

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?

Opens with an explicit trigger: 'Use this when the user has a supplier quote for a part and wants to know if the price is fair.' That gives a clear context for invocation. It stops short of naming alternatives or stating when not to use it (e.g., when no drawing/plan exists), so it falls just below the 5 level.

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

All RFQdecoder 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