Web design Suffolk: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Scored across 3 tools
The three tools have distinct roles: enquiry_describe explains behaviour/consent, enquiry_fields returns the field schema, and submit_enquiry performs the two-step submission. The only mild overlap is that describe and fields are both 'read-before-you-submit' tools, but the descriptions explicitly sequence them ('Read first', 'Pass answers to submit_enquiry').
The names mix conventions: submit_enquiry is verb_noun, enquiry_describe is noun_verb, and enquiry_fields is noun_noun. The shared 'enquiry' prefix makes the set readable and clearly grouped, but the ordering of verb and noun is not predictable.
Three tools is lean but well-matched to a single-purpose enquiry form: one explains the behaviour, one exposes the schema, one submits. The two-phase confirm flow is sensibly folded into one tool rather than spawning extra endpoints.
The surface covers the full lifecycle needed: understanding what happens, knowing the fields, and submitting with consent plus double opt-in confirmation. Minor gaps exist around post-submission status checking or resending the confirmation email, but these are not required for the stated purpose.
Read first. States plainly what submit_enquiry does on Web design Suffolk: it starts an enquiry with Web design Suffolk, 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.
Every field of the Web design Suffolk 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.
Submits an enquiry to Web design Suffolk: 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 Web design Suffolk 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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Web design Sussex: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Web design Guildford: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Web design Basingstoke: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Web design Poole: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Add one secure layer between your agents and this server.