Skip to main content
Glama

Server Details

Medicare Plan Comparison: the site's own MCP server — dataset, enquiry (enquiry = a human...

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation4/5

The dataset tools each target a distinct retrieval shape (schema, exact match, substring search, compare, stats, top-N, provenance), and the enquiry tools split cleanly into explain, field schema, and submit. The only real friction is dataset_row vs dataset_search (exact vs substring) and the two 'read first' directives (dataset_columns and enquiry_describe), which could cause minor ordering confusion but not misselection.

Naming Consistency4/5

All names are snake_case with a clear resource prefix (dataset_*, enquiry_*), which reads predictably. Minor deviation: the mutating tool breaks the prefix pattern as submit_enquiry rather than enquiry_submit, and several dataset_ names use bare nouns (columns, stats) instead of verbs while others use verbs (search, compare, top).

Tool Count5/5

Ten tools is well within the sweet spot. Seven dataset-query tools each cover a genuinely different question shape, and three enquiry tools cover explain/describe/submit without redundancy.

Completeness4/5

Query coverage is strong: schema, provenance, exact lookup, search, comparison, statistics, and ranking all exist, and the enquiry flow has a proper two-step validated submission with consent. Gaps are minor — no grouping/aggregation across columns, no way to check or withdraw a submitted enquiry, and search is capped at 50 rows with no pagination.

Available Tools

10 tools
dataset_columnsDataset columns and shapeAInspect

The columns, which of them are numeric, the row count and the provenance banner of the Medicare Plan Comparison dataset. Call this first to learn the schema.

Inputs: no named parameters.

dataset_compareCompare rows side by sideBInspect

The rows of the Medicare Plan Comparison 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 Medicare Plan Comparison 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 Medicare Plan Comparison dataset where a column equals a value exactly (case-insensitive).

Inputs: value (required), column (required).

dataset_statsSummary statistics for a numeric columnAInspect

count, min, max, mean, median and sum of a numeric column of the Medicare Plan Comparison dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

Inputs: column (required).

dataset_topRank rows by a numeric columnAInspect

The highest (or lowest) rows of the Medicare Plan Comparison 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 Medicare Plan Comparison: 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.

enquiry_fieldsThe questions the enquiry asksAInspect

Every field of the Medicare Plan Comparison 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 human providers (two steps; not a purchase)AInspect

Submits an enquiry to Medicare Plan Comparison: 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: "This site has no form. It does not take your details and passes nothing to anyone."

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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources