Skip to main content
Glama

Server Details

Web design Cheltenham: 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.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: enquiry_describe explains the process and consent, enquiry_fields enumerates the form schema, and submit_enquiry handles validation and submission. The explicit 'Read first' guidance further removes ambiguity about ordering.

Naming Consistency3/5

All names use snake_case, but the patterns are mixed: enquiry_describe and enquiry_fields are noun-first, while submit_enquiry is verb-first. Readable but not a uniform verb_noun convention.

Tool Count5/5

Three tools are well-scoped for a narrow enquiry-submission workflow. Each tool earns its place: explaining the process, listing fields, and submitting the enquiry.

Completeness5/5

The surface covers the full enquiry lifecycle: process description, field schema, and a two-step consented submission with confirmation token. No obvious gaps for this narrow domain.

Available Tools

3 tools
enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)Inspect

Read first. States plainly what submit_enquiry does on Web design Cheltenham: it starts an enquiry with Web design Cheltenham, 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 Web design Cheltenham 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 Web design Cheltenham (two steps; not a purchase)Inspect

Submits an enquiry to Web design Cheltenham: 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 Web design Cheltenham team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."

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