Skip to main content
Glama
Sign In

site

by com.aisandboxenvironments
OverviewDiscussionsAdmin

Server Details

AI Sandbox Environments: 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.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool occupies a distinct stage of one workflow: enquiry_describe explains the process, enquiry_fields returns the schema, and submit_enquiry performs the two-step submission. There is no overlap in purpose or output, and the descriptions explicitly sequence the calls.

Naming Consistency4/5

All names are snake_case, short, and share the 'enquiry' domain token, so intent reads clearly. However, two tools use a noun_verb order (enquiry_describe, enquiry_fields) while the third uses verb_noun (submit_enquiry), a minor ordering inconsistency.

Tool Count5/5

Three tools is exactly right for a single-purpose enquiry form: one to explain, one to expose the field schema, one to submit. Each tool earns its place and nothing feels padded or missing.

Completeness4/5

The lifecycle is well covered: understand, discover fields, validate, confirm, submit, plus a described email-verification follow-up. Minor gaps exist (no way to check enquiry status or withdraw an enquiry), but agents have no dead ends in the core 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 AI Sandbox Environments: it starts an enquiry with AI Sandbox Environments, 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 AI Sandbox Environments 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 AI Sandbox Environments (two steps; not a purchase)AInspect

Submits an enquiry to AI Sandbox Environments: 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 AI Sandbox Environments team sees it. Consent means the person has read and agreed to: "I agree that the people who run this site read my environment details and reply to me."

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
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources