Wedding Cost Checker: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
Scored across 10 tools
The dataset tools are mostly distinct: schema, provenance, exact-row lookup, substring search, statistics, top/bottom ranking, and multi-value comparison each have a clear role. The main overlap risk is among dataset_row, dataset_compare, dataset_search, and dataset_top, since all retrieve rows, but their descriptions give enough cues for correct selection.
All names use lowercase snake_case and a clear domain prefix scheme: dataset_* for data access, enquiry_* for enquiry metadata, and submit_enquiry for the action. The suffixes mix nouns and verbs (e.g., dataset_columns vs dataset_compare), so the action pattern is not fully uniform, but the grouping remains readable and predictable.
Ten tools is well within the ideal range and each appears to earn its place: seven cover dataset inspection and querying, while three cover the enquiry workflow. The surface is not bloated, and no tool looks obviously redundant.
The dataset surface covers schema, provenance, exact lookup, search, statistics, ranking, and comparison, while the enquiry side covers explanation, field schema, and a two-step submission flow. Minor gaps remain, such as a general multi-condition filter/list-all operation and any enquiry status or cancellation lookup, but core workflows are covered.
The columns, which of them are numeric, the row count and the provenance banner of the Wedding Cost Checker dataset. Call this first to learn the schema.
Inputs: no named parameters.
The rows of the Wedding Cost Checker dataset whose column is any of the given values, in the order given, for "X vs Y" questions.
Inputs: column (required), values (required).
The source, the date it was computed, the licence and the citation for the Wedding Cost Checker dataset. Read this to attribute a figure correctly.
Inputs: no named parameters.
The rows of the Wedding Cost Checker dataset where a column equals a value exactly (case-insensitive).
Inputs: value (required), column (required).
Rows of the Wedding Cost Checker dataset whose cells contain the query (case-insensitive), up to 50.
Inputs: query (required), limit.
count, min, max, mean, median and sum of a numeric column of the Wedding Cost Checker dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).
Inputs: column (required).
The highest (or lowest) rows of the Wedding Cost Checker dataset by a numeric column: "which is the most/least X".
Inputs: column (required), limit, ascending.
Read first. States plainly what submit_enquiry does on Wedding Cost Checker: 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 Wedding Cost Checker 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 Wedding Cost Checker: 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: "By sending this you agree the Wedding Cost Checker team reads your enquiry and replies by email. We do not pass it to anyone else."
Inputs: answers (required), consent (required), confirmation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Med Spa Cost Checker: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
Procedure Cost Checker: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
Equipment Rental Compare: the site's own MCP server — dataset, enquiry (enquiry = a human...
Card Machine Pricing: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
Add one secure layer between your agents and this server.