Skip to main content
Glama

Server Details

ISO Certification 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 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.4/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: enquiry_describe explains the process/consent, enquiry_fields returns the schema, and submit_enquiry performs the actual submission. The descriptions explicitly state 'read first' and 'pass answers to submit_enquiry', leaving little room for misselection.

Naming Consistency3/5

All names are snake_case and share the 'enquiry' token, but the verb position is inconsistent: 'enquiry_describe' and 'enquiry_fields' are noun-first while 'submit_enquiry' is verb-first. Readable, but a mixed convention across a three-tool set.

Tool Count5/5

Three tools is exactly right for a single-purpose enquiry-submission flow: one to explain, one to expose the schema, one to submit. Each earns its place and nothing is padded.

Completeness4/5

The describe/fields/submit triangle covers the core lifecycle, including two-step consent and token confirmation, with the follow-up email link handling post-submission state. Minor gaps exist (no way to check enquiry status or withdraw consent after submission), but these are workable given the email-driven flow.

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 ISO Certification 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 ISO Certification 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 ISO Certification 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 relevant ISO consultants and certification bodies, chosen by ISO Certification 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