Broker vs Advisor: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...
Scored across 6 tools
The checker_* tools and enquiry_* tools target clearly different resources, and submit_enquiry is distinct from the read-only enquiry tools. However, checker_tree overlaps with checker_start/checker_answer by exposing the full guide statically, and enquiry_describe overlaps slightly with enquiry_fields on consent and enquiry metadata.
All names are snake_case and readable, but the verb/noun ordering is mixed: checker_answer and checker_start are noun_verb, enquiry_fields is noun_noun, and submit_enquiry is verb_noun. The two prefix families are understandable, but the set does not follow one predictable pattern.
Six tools are well scoped for a decision guide plus an enquiry form. Each tool has a clear role, and the count is neither thin nor heavy.
The guide is covered from start through answer to full tree, and the enquiry flow covers description, field schema, validation, consent, and final submission. No obvious lifecycle operation is missing for the stated site purpose.
Given a question id and the chosen option (its choice index), return the next question or the final verdict.
Inputs: choice (required), question (required).
The first question of the Which model should sell your business? decision guide.
Inputs: no named parameters.
Every question, option and verdict of the Which model should sell your business? guide, for reasoning end to end.
Inputs: no named parameters.
Read first. States plainly what submit_enquiry does on Broker vs Advisor: 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 Broker vs Advisor 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 Broker vs Advisor — 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: "Your enquiry goes only to the team behind this site, who'll contact you directly. It is not passed to any broker or adviser."
Inputs: answers (required), consent (required), confirmation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Business Value Now: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...
Own vs Charter: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
HMO Licence Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...
Compare Answering: the site's own MCP server — compare, enquiry (enquiry = a human handoff, not...
Add one secure layer between your agents and this server.