Web design Poole: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Scored across 3 tools
Each tool has a clearly distinct role: describe the process, list the enquiry fields, and submit the enquiry. The descriptions explicitly sequence them and explain when to use each, leaving little room for misselection.
All names use snake_case, but the pattern mixes noun-first and verb-first forms: enquiry_describe, enquiry_fields, submit_enquiry. The names are still readable and domain-scoped, but they do not follow a single predictable convention.
Three tools are appropriately scoped for a narrow enquiry-submission workflow. Each tool has a necessary function, and there are no redundant operations.
The tool set covers the core lifecycle: understanding the process, retrieving the field schema, validating, and submitting with consent and a confirmation token. Minor gaps exist around checking submission status or resending the verification email, but the main workflow is complete.
Read first. States plainly what submit_enquiry does on Web design Poole: it starts an enquiry with Web design Poole, 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 Poole 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 Poole: 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 Poole 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 Basingstoke: 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 Suffolk: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Web design Sussex: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Add one secure layer between your agents and this server.