Skip to main content
Glama

site

by uk.co.commercialdrainagequotes

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

submit_enquiry

Submits an enquiry to Commercial Drainage Quotes — 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 commercial drainage contractors, who'll quote the work 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 commercial drainage contractors, who'll quote the work 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.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and meets it: it discloses a two-step call pattern, that Step 1 does not submit, that a confirmation token from Step 1 is required, that submission sends an email, and that providers see nothing until the link is clicked. It also provides the exact consent text and its meaning.

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?

The description is front-loaded with the most important caveats and then organizes the body into Step 1 and Step 2. It is dense but every sentence carries operational information; there is no filler.

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?

For a two-step tool with no output schema and no annotations, this description is complete: it explains return values from Step 1, the condition for Step 2, the email verification event, and the exact consent statement. An agent has enough information to call it correctly and know what to relay to the person.

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

Parameters5/5

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

Though schema coverage is 100%, the description materially enriches parameter meaning: answers must be keyed by enquiry_fields keys, consent must be true and carries a specific legal agreement, and confirmation is specifically the token returned by Step 1 after approval. This makes parameter usage unambiguous.

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 states a specific operation with a clear resource ('Submits an enquiry to Commercial Drainage Quotes') and immediately distinguishes what it is not ('NOT a purchase, NOT a guaranteed quote'). The two-step validation-then-submit flow clarifies the verb 'submit' and makes the tool distinguishable from siblings like 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 Guidelines4/5

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

The description gives an explicit when-to-use sequence: Step 1 for validation and token, Step 2 only if the person agrees. It also references enquiry_fields as the source of answer field keys, linking to the right sibling. It lacks a direct 'use X instead' statement, but the step gating and exclusions are effectively usage guidance.

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.2/5.0
Disambiguation5/5

Each tool has a clearly distinct role: enquiry_describe explains the process, enquiry_fields provides the input schema, and submit_enquiry performs the actual submission/confirmation flow. There is little risk of selecting the wrong tool for a given step.

Naming Consistency3/5

All names use snake_case and are readable, but the pattern is not fully consistent: enquiry_describe and enquiry_fields place the noun first while submit_enquiry uses verb-first ordering. This is a minor stylistic mismatch rather than a usability problem.

Tool Count5/5

Three tools is an appropriate scope for a focused enquiry-submission server. Each tool provides a necessary part of the workflow: understanding the process, retrieving the field schema, and submitting with a confirmation step.

Completeness5/5

The tool set covers the full enquiry flow: describing the process, defining the fields, validating answers, obtaining consent, and completing submission with a confirmation token. There are no obvious missing operations for the stated purpose of submitting a commercial drainage quote enquiry.

Resources