site

The three tools occupy clearly separate steps of a single workflow: enquiry_describe explains the process, enquiry_fields returns the schema, and submit_enquiry performs the action. Descriptions explicitly sequence them ("Read first", "Pass answers to submit_enquiry keyed by field key"), leaving no realistic chance of misselection.

Two tools use a noun-first 'enquiry_' prefix (enquiry_describe, enquiry_fields) while the action tool uses verb-first 'submit_enquiry'. Each name is readable and the shared 'enquiry' token helps grouping, but the verb/noun ordering convention is not consistent across the set.

Three tools is lean but defensible for a single-purpose enquiry form server, and each one maps to a distinct step (explain, inspect schema, submit). The describe/fields pair could arguably be merged into one 'get form definition' tool, but the split is justified by the explicit read-first guidance.

The surface covers the full public-facing lifecycle: understanding consent, discovering fields, validating, and a two-step confirmed submission with a double-opt-in email. There is no way to check enquiry status or resume a pending confirmation, but for an anonymous lead-capture form those gaps are minor and largely handled out-of-band by email.