Skip to main content
Glama

Server Details

Fire Risk Quotes: the site's own MCP server — 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

A4.5/5.0

Scored across 3 tools

Disambiguation4/5

The three tools have distinct roles: enquiry_describe explains the process, enquiry_fields returns the form schema, and submit_enquiry performs the submission. The two read-side tools (describe vs fields) are close enough that an agent might briefly hesitate, but the descriptions clearly differentiate process explanation from field listing.

Naming Consistency4/5

All three names share the 'enquiry' token and use a noun_verb or verb_noun pattern that is readable and predictable. The slight inconsistency is that two are prefixed enquiry_ while the submit tool uses the suffix form, a minor deviation rather than a break.

Tool Count5/5

For a single narrow domain (submitting one enquiry form), three tools is exactly right: describe the flow, enumerate the fields, then submit. Each tool earns its place with no redundancy or bloat.

Completeness4/5

The surface covers the full enquiry lifecycle: explaining intent, exposing the field schema, and a two-step consent-based submission. There is no status/confirmation-check tool, but the described email-link verification flow makes that a minor gap agents can work around.

Available Tools

3 tools
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 Fire Risk Quotes: 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 Fire Risk Quotes 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 Fire Risk Quotes — 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: "Send my contact details to up to three relevant fire risk assessors, chosen by Fire Risk Quotes, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

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