Skip to main content
Glama

Server Details

RMMCompare: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...

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.5/5.0

Scored across 10 tools

Disambiguation4/5

The dataset tools split into clearly-motivated operations (schema, provenance, exact row, substring search, multi-value compare, stats, top-N), and the descriptions explicitly distinguish exact-match from contains-match from any-of matching. The only residual confusion is between dataset_row, dataset_search and dataset_compare, which all retrieve rows by value and differ mainly in matching semantics. The enquiry trio is cleanly separated into explain, schema, and two-step submit.

Naming Consistency4/5

All names are snake_case with a consistent resource prefix (dataset_*, enquiry_*) plus submit_enquiry, so grouping is immediately readable. The suffix style mixes nouns (dataset_columns, dataset_row, enquiry_fields) with action-ish words (dataset_search, dataset_compare, dataset_top), but it never becomes cryptic. Minor deviation only: submit_enquiry uses verb_noun while the rest are noun-oriented.

Tool Count5/5

Ten tools is a well-scoped set: seven read-only dataset accessors covering distinct query shapes, two meta tools for the enquiry schema and meaning, and one submit action. Each tool has an evident, non-redundant role and nothing feels padded or missing at the count level.

Completeness4/5

The read side has strong coverage: schema introspection, provenance/citation, exact lookup, free-text search, multi-value comparison, numeric aggregates and top/bottom ranking — enough for most analytical questions without dead ends. Minor gaps: no way to combine multiple predicates in a single query, no group-by/categorical aggregation, and no enquiry status or retrieval tool after submission.

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 RMMCompare dataset. Call this first to learn the schema.

Inputs: no named parameters.

dataset_compareCompare rows side by sideBInspect

The rows of the RMMCompare 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 RMMCompare dataset. Read this to attribute a figure correctly.

Inputs: no named parameters.

dataset_rowLook a row up by an exact keyCInspect

The rows of the RMMCompare dataset where a column equals a value exactly (case-insensitive).

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

dataset_statsSummary statistics for a numeric columnBInspect

count, min, max, mean, median and sum of a numeric column of the RMMCompare 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 RMMCompare 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 RMMCompare: 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 RMMCompare 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 RMMCompare: 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 submitting you agree RMMCompare emails you a recommendation and shares nothing else with 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