Skip to main content
Glama
Sign In

Vibe Manufacturing

by com.vibe-manufacturing
OverviewDiscussionsAdmin

Create a quote request (RFQ)

create_rfq
Destructive

Create a structured request for quotation for the human you act for. Call get_rfq_requirements for the process first and upload files with upload_rfq_file; use dry_run to check completeness before sending. The answer contains quote_readiness, missing and recommended items. We match manufacturers, email the ones that opted in, and return direct contact, quote-form and agent links for all matches plus an RFQ id and a token to read quotes later. Only call after the user agreed that the request is shared with matched manufacturers.

Input Schema

NameRequiredDescriptionDefault
finishNo
strictNotrue = refuse to send when required items are missing
dry_runNotrue = check completeness only; nothing is stored or sent
processYes
file_idsNofile_id values returned by upload_rfq_file
quantityYes
cad_filesNo
materialsNo
needed_byNo
industriesNo
budget_noteNo
descriptionYesPart, size, material, use
callback_urlNoOptional https URL that receives a signed event when a factory answers
file_formatsNo
thickness_mmNoMaterial thickness for sheet, plate and cut parts
tolerance_mmNo
user_consentNotrue only if the user agreed to share the request with matched manufacturers; required unless dry_run
certificationsNo
requester_emailNoReply address of the human requester; required unless dry_run
ship_to_countryNoISO 3166-1 alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / requester_email / description
      Added value: +"Reply address of the human requester; required unless dry_run"
    • changedInput schema / properties / user_consent / description
      Previous value: -"true only if the user agreed to share the request with matched manufacturers"New value: +"true only if the user agreed to share the request with matched manufacturers; required unless dry_run"
    • changedInput schema / required
      Previous value: -[
-  "process",
-  "quantity",
-  "description",
-  "requester_email",
-  "user_consent"
-]New value: +[
+  "process",
+  "quantity",
+  "description"
+]
  2. Changed5 schema fields changed
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Optional https URL that receives a signed event when a factory answers",
+  "type": "string"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true = check completeness only; nothing is stored or sent",
+  "type": "boolean"
+}
    • addedInput schema / properties / file_ids
      Added value: +{
+  "description": "file_id values returned by upload_rfq_file",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • addedInput schema / properties / strict
      Added value: +{
+  "description": "true = refuse to send when required items are missing",
+  "type": "boolean"
+}
    • addedInput schema / properties / thickness_mm
      Added value: +{
+  "description": "Material thickness for sheet, plate and cut parts",
+  "type": "number"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / certifications / items / enum
      Previous value: -[
-  "iso-9001",
-  "iso-14001",
-  "iatf-16949",
-  "iso-13485",
-  "as9100",
-  "en-1090",
-  "iso-45001"
-]New value: +[
+  "iso-9001",
+  "iso-14001",
+  "iatf-16949",
+  "iso-13485",
+  "as9100",
+  "en-1090",
+  "iso-45001",
+  "itar",
+  "nadcap",
+  "ul-listed",
+  "rohs",
+  "fda-registered",
+  "cmmc"
+]
    • changedInput schema / properties / process / enum
      Previous value: -[
-  "laser-cutting",
-  "cnc-machining",
-  "sheet-metal",
-  "3d-printing",
-  "injection-molding",
-  "pcb-assembly",
-  "die-casting",
-  "welding",
-  "waterjet-cutting",
-  "metal-stamping",
-  "surface-finishing"
-]New value: +[
+  "laser-cutting",
+  "cnc-machining",
+  "sheet-metal",
+  "3d-printing",
+  "injection-molding",
+  "pcb-assembly",
+  "die-casting",
+  "welding",
+  "waterjet-cutting",
+  "metal-stamping",
+  "forging",
+  "heat-treatment",
+  "grinding-polishing",
+  "casting",
+  "wire-forming",
+  "steel-construction",
+  "surface-finishing"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the write/destructive/ non-idempotent profile, so the description correctly focuses on added context: manufacturers are matched, opted-in ones emailed, and quote/form/agent links are returned. It surfaces a consent precondition, which annotations cannot express. Minor gaps: no rate limits or failure semantics described.

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?

Three sentences, front-loaded with the core action and prerequisites. The last sentence adds the important consent guard. No padding, though sentence two is somewhat dense with multiple ideas run together.

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 20-parameter write tool with no output schema, the description covers prerequisites, side effects, and the response shape (quote_readiness, missing, links). Missing detail on how matching criteria (industries, materials, certifications) affect the outcome and pagination/auth considerations.

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?

Schema description coverage is only 45% but the schema compensates with enums and inline descriptions. The description explains the purpose of dry_run and the consent gate, but does not add anything about the many untyped parameters (finish, materials, needed_by, industries, etc.). Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('Create a structured request for quotation') and distinguishes itself from siblings like submit_quote or get_rfq. The distinction from submit_quote_request is not made explicit, though the two are close in intent.

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?

Names prerequisite steps (get_rfq_requirements first, upload_rfq_file for files) and a precondition that must hold before calling ('Only call after the user agreed...'). However, it does not explicitly contrast with the sibling submit_quote_request, which is the most natural alternative to mention.

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

All Vibe Manufacturing 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