MCP server for AuraVMS — run RFQ/procurement cycles from any MCP-capable agent: add suppliers, create and send RFQs, pull quotes with L1/L2/L3 ranking, place orders, close out.
AuraVMS MCP demonstrates solid tool design with clear naming (verb_noun pattern), comprehensive descriptions (avg 180 chars), and well-structured Zod schemas. All 8 tools have explicit descriptions and input schemas with type definitions. Safety-critical tools (create_rfq, place_order) include explicit confirmation/draft defaults. However, output schemas are not documented, responses are returned as raw API payloads without field descriptions. Parameter descriptions are generally good but lack format constraints (e.g., email validation, date formats). Error handling is basic (generic API errors) without recovery guidance. Missing tool annotations (readOnlyHint, destructiveHint, idempotentHint) for agent planning.
Add a new supplier to the AuraVMS account. Searches for the email first (supplier emails are unique — re-adding an existing vendor fails). Returns the supplier UUID to use in create_rfq.
Close an RFQ (mark as closed, no more quotes accepted). Use after all orders are placed.
Create an RFQ in AuraVMS. SAFETY: by default this saves a DRAFT and emails nobody. Pass send:true ONLY after the user has explicitly confirmed — sending emails a zero-signup quote link to every invited supplier. Supplier IDs come from list_suppliers / add_supplier.
Get quotes for an RFQ item (L1/L2/L3 ranking by price, lead time, quality score). Supplier responses are ranked automatically; use this to pull ranked quotes and decide which to accept.
List RFQs (filter by status open/closed, search, paginate). Pass rfq_id to get one RFQ's items and per-supplier response status (has_responded / is_declined — answers 'who hasn't responded?'). Item ids feed get_quotes.
Output schemas not documented. Tools return raw API responses without field descriptions, forcing LLMs to infer structure. Downstream tools cannot reliably extract IDs for chaining.
Missing tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from irreversible writes without parsing descriptions.
Error handling lacks recovery guidance. API errors return raw messages without actionable next steps (e.g., 'Supplier email already exists, call list_suppliers to verify').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Search or list suppliers in the AuraVMS account. Use before add_supplier (supplier emails are unique) and to collect supplier UUIDs for create_rfq.
Place an order from an accepted quote. SAFETY: requires confirm:true (it emails a purchase order to the supplier). Use after get_quotes and user approval.
Send reminder emails to suppliers who haven't responded to an RFQ. Throttled to once per RFQ per 24h (in-process guard).
Parameter descriptions lack format constraints. 'email' field has .email() validation but description does not state format. 'date' fields in items array lack ISO 8601 specification.
Result limits not enforced or documented. list_suppliers and list_rfqs accept page_size up to 100 but no guidance on recommended defaults or max results per call.