Skip to main content
Glama

site

by uk.co.threephasecost

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Three Phase 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: "Happy for my details to go to electrical contractors and connection providers, who'll quote me directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to electrical contractors and connection providers, who'll quote me directly.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the two-step validation flow, the email notification with a clickable link, the consent requirement, and that this is not a purchase or guaranteed quote. It also reproduces the exact consent statement so the agent knows what 'consent' means in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although the description is longer than average, every sentence earns its place by explaining a required step, a constraint, or an exclusion. The key warnings ('NOT a purchase, NOT a guaranteed quote') are front-loaded, and the step-by-step structure makes the flow easy to follow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the absence of annotations, and the absence of an output schema, the description is remarkably complete. It explains both call phases, the expected outputs of each phase, the consent text, and the post-submission email-link behavior. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds meaning by clarifying that answers come from enquiry_fields keys, that confirmation is the step-1 token, and that consent must match the exact stated agreement. This enriches the schema without repeating it verbatim.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Submits an enquiry to Three Phase Cost'. It explicitly distinguishes itself from a purchase and a guaranteed quote, and the title highlights the two-step nature. This clearly separates it from the sibling read-only tools enquiry_describe and enquiry_fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: call first with answers and consent=true to validate and receive a confirmation token, then call again only if the person agrees. It names the required precondition for the second call and warns that the enquiry is not visible to providers until the person clicks the emailed link. This leaves no ambiguity about sequencing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct role: enquiry_describe explains the overall process and consent, enquiry_fields provides the exact schema, and submit_enquiry performs the two-step submission. There is no functional overlap between them.

Naming Consistency3/5

All names are lowercase snake_case, but the pattern is mixed: enquiry_describe and enquiry_fields are enquiry-first, while submit_enquiry is verb-first. The names are still readable, but the set is not consistently verb_noun.

Tool Count5/5

Three tools is appropriate for the narrow scope of submitting an enquiry: describe the process, get the fields, submit. Each tool earns its place and none are redundant.

Completeness5/5

The server covers the full enquiry submission flow: explaining the process, fetching the required field definitions, and performing the validated two-step submission with consent and confirmation token. No obvious gaps exist for the stated purpose.

Resources