site
Server Details
Insurance by Profession: the site's own MCP server — dataset, enquiry (enquiry = a human...
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
The dataset query tools are mostly distinguished by matching semantics (exact equality via dataset_row, substring via dataset_search, ordered multi-value via dataset_compare), and the descriptions spell these out. There is mild residual overlap: dataset_columns returns a 'provenance banner' while dataset_provenance covers attribution, and row/search/compare could be confused by a careless agent.
Nine of ten tools follow a clean namespace_noun pattern (dataset_*, enquiry_*), which makes grouping obvious. The outlier is submit_enquiry (verb-first, separate from the enquiry_ prefix), a minor deviation in an otherwise predictable scheme.
Ten tools is well within the sweet spot, and each earns its place: seven narrow read operations over one dataset plus three tools covering the enquiry lifecycle. Nothing feels redundant or padded.
The read surface is unusually thorough (schema, provenance, exact/substring/multi-value lookup, stats, ranking) and the enquiry flow covers describe, fields, validate and two-step confirm-and-submit. The main gap is that there is no way to enumerate distinct values or group by a categorical column, which 'which profession has the most X' style questions would sometimes need.
Available Tools
10 toolsdataset_columnsDataset columns and shapeAInspect
The columns, which of them are numeric, the row count and the provenance banner of the Insurance by Profession dataset. Call this first to learn the schema.
Inputs: no named parameters.
dataset_compareCompare rows side by sideBInspect
The rows of the Insurance by Profession dataset whose column is any of the given values, in the order given, for "X vs Y" questions.
Inputs: column (required), values (required).
dataset_provenanceWhere this data comes from, and how to cite itAInspect
The source, the date it was computed, the licence and the citation for the Insurance by Profession dataset. Read this to attribute a figure correctly.
Inputs: no named parameters.
dataset_rowLook a row up by an exact keyBInspect
The rows of the Insurance by Profession dataset where a column equals a value exactly (case-insensitive).
Inputs: value (required), column (required).
dataset_searchSearch the datasetAInspect
Rows of the Insurance by Profession dataset whose cells contain the query (case-insensitive), up to 50.
Inputs: query (required), limit.
dataset_statsSummary statistics for a numeric columnAInspect
count, min, max, mean, median and sum of a numeric column of the Insurance by Profession dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).
Inputs: column (required).
dataset_topRank rows by a numeric columnBInspect
The highest (or lowest) rows of the Insurance by Profession dataset by a numeric column: "which is the most/least X".
Inputs: column (required), limit, ascending.
enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect
Read first. States plainly what submit_enquiry does on Insurance by Profession: it starts an enquiry with Insurance by Profession, whose team reads it and replies 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.
enquiry_fieldsThe questions the enquiry asksAInspect
Every field of the Insurance by Profession 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.
submit_enquirySubmit an ENQUIRY to Insurance by Profession (two steps; not a purchase)AInspect
Submits an enquiry to Insurance by Profession: 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 the Insurance by Profession team sees it. Consent means the person has read and agreed to: "By sending this you agree the Insurance by Profession team reads your message and replies by email. We do not pass it to an insurer, a broker or anyone else."
Inputs: answers (required), consent (required), confirmation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Structured Settlement Compare: the site's own MCP server — dataset, enquiry (enquiry = a human...
Commercial Refinance Quotes: the site's own MCP server — dataset, enquiry (enquiry = a human...
Medicare Plan Comparison: the site's own MCP server — dataset, enquiry (enquiry = a human...
Answering Service Quotes: the site's own MCP server — dataset, enquiry (enquiry = a human...
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.312 npmMIT
- AlicenseNot gradedqualityDmaintenanceUS + EU salary benchmarking, pay transparency compliance, and semantic endpoints. 1,400+ US occupations, 28 EU countries. MCP server for AI agents.MIT
- AlicenseCqualityCmaintenanceA research MCP server for UK geospatial and statistical data, enabling AI assistants to query Ordnance Survey and ONS datasets.1033MIT
- AlicenseAqualityDmaintenanceMedical terminology MCP server — ICD-10, MedDRA, RxNorm, CTCAE for AI agents620 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.