
Electrical design and RFQs
Voltformer helps users search electrical equipment, compare transformer specifications, read technical articles and perform preliminary engineering calculations. Connect a Voltformer account to manage projects, company profiles and product shortlists; create and edit single-line diagrams; run available studies; export drawings; and submit quotation requests after confirmation.
Example path → ·
https://voltformer.com/mcpFor government procurement discovery use queryGovernmentTenders then getGovernmentTender. These public read-only tools query selected source-reviewed notices within the returned coverage dates, not exhaustive worldwide or live coverage. Cite source.url, retain evidence and unknowns, and verify amendments, eligibility and deadlines on the authoritative portal. They do not submit bids. For engineering drawings, call getSldCapabilities, listProjects, then createSldDocument. Use getSldDocument/saveSldDocument for all editor data including equipment placement, wires, labels, sheets and studies. Preserve snapshot fields. All existing-drawing writes require both expectedVersion (storageVersion) and expectedCreatedAt (createdAt) from the last read, protecting against concurrent edits and a deleted/recreated ID. Link exact catalog SKUs with linkSldCatalogProduct; analyzeSldDocument returns the same study engine and limitations as the editor. exportSldDocument returns SVG/DXF/JSON/CSV/Python/report content or PNG/PDF as base64. createSldRevision archives a snapshot; duplicateSldDocument and syncSldProjectEquipment match member workflows. Never mark a drawing APPROVED without the user explicitly requesting that status. Use getCatalogTaxonomy before category-sensitive discovery to understand the Power & Energy Equipment domain and its engineering product-family hierarchy. Voltformer electrical-equipment catalog. Public discovery covers transformers (queryTransformers/getProductBySlug), switchgear (querySwitchgear/getSwitchgearBySlug), protection/control (queryProtectionControl/getProtectionControlBySlug), generators (queryGenerators/getGeneratorBySlug), grid equipment and PV inverters (queryGridEquipment/getGridEquipmentBySlug), and solar modules (querySolar/getSolarBySlug). Discover exact catalog identifiers before calculations or RFQs. Transformer comparisons, kVA sizing and loss ROI apply only to transformers. With a connected member account (agent key or OAuth 2.1, discovery: /.well-known/oauth-protected-resource/mcp) you can do everything the member does in the web UI: manage company profiles (listCompanyProfiles/upsertCompanyProfile/deleteCompanyProfile), manage projects and link quotations to them (listProjects/upsertProject/getProject/deleteProject, then pass projectId to submitRfqQuoteRequest), maintain the product shortlist (listFavorites/setFavorites), track RFQ requests and their results (listRfqs, optionally scoped with projectId) and handle technical-specification PDFs end to end (createSpecificationUploadUrl + finalizeSpecificationUpload before submitting, getRfqSpecificationDownloadUrl to read them back). For RFQs, first call listCompanyProfiles, listProjects and catalog search to prefill known data. Before submission you must ask for: named contact (phone is optional), project name, exact SKU and quantity, delivery term and requested date (or explicitly flexible), supply/installation/commissioning scope, whether a technical-specification PDF exists, site-condition status, and whether each selected catalog model is accepted without deviation. For DAP/DDP/site delivery, city and full delivery address are required. If catalog specifications are not accepted, collect the deviations or attach the PDF. Unknown optional fields must be omitted, never sent as null or undefined. Never choose between multiple catalog matches on the user’s behalf. If a family/power description matches different primary or secondary voltages, technologies, windings or configurations, present the alternatives and ask the user to select the exact SKU. Do not silently substitute a near match. Technical specifications must be PDF. Tell the user before requesting one: chat-inline upload accepts at most 5 MiB; the signed upload URL flow accepts at most 80 MiB. If the MCP client exposes attachment bytes, call uploadSpecificationInline and attach its returned metadata. Otherwise use createSpecificationUploadUrl, PUT application/pdf bytes, then finalizeSpecificationUpload. Never claim a chat attachment was uploaded unless a tool returned validated=true. submitRfqQuoteRequest creates a durable RFQ and requires a valid X-Voltformer-Agent-Key header or OAuth 2.1 authorization (discovery: /.well-known/oauth-protected-resource/mcp); it is never anonymous. Always show a complete final summary containing company/contact, project, each exact SKU and quantity, voltage/configuration acceptance or deviations, delivery destination/term/date, installation scope, specification status, site-condition status, budget/urgency if supplied, and all warnings. Obtain explicit user confirmation immediately before calling it and only then set userConfirmed=true. Never infer confirmation from earlier messages. Retry failed submissions with the same Idempotency-Key to avoid duplicates. Final electrical design requires site-specific verification.
3 in the ChatGPT listing