site
Server Details
EPOS system for retail: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools form a clean pipeline with no overlap: enquiry_describe explains the process, enquiry_fields returns the schema, and submit_enquiry performs the action. Descriptions and sequencing cues ('Read first', 'Step 1/Step 2') make misselection very unlikely.
All tools share the 'enquiry' prefix, giving a readable grouping, but the verb placement is inconsistent: enquiry_describe and enquiry_fields are noun_verb while submit_enquiry is verb_noun. It's understandable but not a predictable single convention.
Three tools is exactly right for a single-purpose, low-complexity enquiry funnel: explain, expose schema, submit. Nothing feels padded or missing for the stated scope.
The submit lifecycle is fully covered, including validation, consent wording, and a two-step confirmation token flow. There is no way to check enquiry status or retrieve a previous submission, but that is arguably outside the form-filling person's scope.
Available Tools
3 toolsenquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect
Read first. States plainly what submit_enquiry does on EPOS system for retail: it starts an enquiry with EPOS system for retail, whose team reads it and replies directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
Inputs: no named parameters.
enquiry_fieldsThe questions the enquiry asksAInspect
Every field of the EPOS system for retail enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
Inputs: no named parameters.
submit_enquirySubmit an ENQUIRY to EPOS system for retail (two steps; not a purchase)AInspect
Submits an enquiry to EPOS system for retail: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before the EPOS system for retail team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."
Inputs: answers (required), consent (required), confirmation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
MCP server for Support & Service Management
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for e-commerce operations including product catalog management, cart/checkout, and Stripe integration, with built-in EU AI Act compliance.71 PyPIMIT

inflow-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP Server for agents to onboard, pay, and provision services autonomously with InFlow6MIT- AlicenseBqualityDmaintenanceMCP server for Maasy AI Marketing Copilot2179 npmMIT
- AlicenseNot gradedqualityDmaintenanceAI customer support MCP server with order status lookup and RAG-powered knowledge base search for e-commerce stores.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.