Render Cost Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
Scored across 5 tools
Each tool has a clearly distinct role: calculate runs the calculator, calculator_describe explains its inputs/outputs, enquiry_describe explains consent and submission semantics, enquiry_fields lists the enquiry schema, and submit_enquiry performs validation/submission. Although enquiry_describe and enquiry_fields both describe enquiry-related information, their descriptions make the split clear.
The names are readable but mix conventions: calculate is a bare verb, calculator_describe/enquiry_describe use resource_verb, enquiry_fields is resource_noun, and submit_enquiry uses verb_resource. Domain prefixes help, but verb placement is inconsistent across the set.
Five tools is well scoped for a calculator plus enquiry-submission site: one calculation tool, two descriptive/schema tools for the calculator, and two enquiry workflow tools. Each tool earns its place without obvious redundancy.
The surface covers the core calculator and enquiry lifecycle: run calculation, inspect inputs/assumptions, inspect enquiry fields/semantics, and submit an enquiry with validation and confirmation. Minor possible gaps exist around post-submission status or withdrawal operations, though those may be handled outside the tool surface via email.
Run the House rendering cost calculator calculator: Wall area used; Low end of typical 2026 quotes; High end of typical 2026 quotes. Missing inputs fall back to their documented defaults.
Inputs: area, scaffold, houseType, renderType.
The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.
Inputs: no named parameters.
Read first. States plainly what submit_enquiry does on Render Cost Calculator: 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 Render Cost Calculator 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 Render Cost Calculator — 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 local rendering specialists, chosen by Render Cost Calculator, 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…
Scaffolding Cost Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
IT Support Cost Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
Employer Cost Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
Contractor Pay Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
Add one secure layer between your agents and this server.