Skip to main content
Glama

Server Details

Freight Insurance Cost: 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. 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.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a sharply distinct role in a single pipeline: enquiry_describe explains the process and consent, enquiry_fields enumerates the form schema, and submit_enquiry performs the two-step submission. There is no overlap in purpose and the descriptions explicitly sequence them ('Read first', 'Pass answers to submit_enquiry').

Naming Consistency5/5

All three names are snake_case and share a consistent 'enquiry_' domain prefix with a clear action verb or noun (describe, fields, submit). The pattern is predictable and readable.

Tool Count4/5

Three tools is on the lean side but matches a narrowly scoped single-form enquiry server; each tool earns its place with no filler. It is not thin enough to be a mismatch, though there is little room for growth.

Completeness4/5

The surface covers the full lifecycle for this domain: understand the offer, discover required fields, and submit with consent plus confirmation-token verification. Minor gaps exist around checking enquiry status or retracting a submission, but those are handled out-of-band via the confirmation email link.

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 Freight Insurance Cost: 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 Freight Insurance Cost 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 Freight Insurance Cost: 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 freight forwarding and sourcing firms, chosen by Freight Insurance Cost, 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