Heritage Statement Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Scored across 3 tools
enquiry_describe (behavior/what the flow does), enquiry_fields (field schema), and submit_enquiry (the actual submission) each have a distinct role and the descriptions reinforce the boundaries. The two read-only introspection tools could be momentarily conflated, but their content is clearly different.
All names are snake_case and easy to read, but the convention mixes a noun-prefix pattern (enquiry_describe, enquiry_fields) with a verb-prefix pattern (submit_enquiry). This is a minor stylistic deviation rather than real confusion.
Three tools is a tight, well-scoped set for a single-purpose enquiry flow with a two-step consent cycle, and each tool does real work. It sits at the thin end of the range but nothing feels redundant or missing for the stated scope.
The surface covers discover-the-flow, discover-the-fields, and a two-step validated submission with consent and confirmation token, which is complete for submitting an enquiry. There is no way to check the status of a previously submitted enquiry or cancel a request, a minor gap users may hit later.
Read first. States plainly what submit_enquiry does on Heritage Statement Cost: it starts an enquiry with human providers who quote 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 Heritage Statement Cost 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 Heritage Statement Cost — 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 any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three heritage consultants, chosen by Heritage Statement Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
Inputs: answers (required), consent (required), confirmation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Structural Report Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Site Investigation Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Transport Statement Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Underpinning Costs: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Add one secure layer between your agents and this server.