Skip to main content
Glama

site

by uk.co.voidclearancequotes

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

submit_enquiry

Submits an enquiry to Void Clearance 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 registered waste carriers and clearance contractors, who'll quote 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 registered waste carriers and clearance contractors, who'll quote 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.7/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 does so well. It discloses that this is not a purchase, requires explicit consent with quoted wording, sends an email, and that providers only see the enquiry after the person clicks the emailed link. It also reveals the two-step confirmation behavior.

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 core action and key exclusions, then organized into clear step 1 and step 2 flow. The quoted consent line is necessary context, and every sentence contributes to correct invocation.

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?

Despite having no annotations and no output schema, the description fully equips an agent to handle the two-step flow: what to send, what to show the person, when to call again, and what happens after submission. It also references the sibling tool for field keys, making the integration context complete.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by specifying that answers must be keyed by field key from enquiry_fields, that consent must be true only when the person has agreed to the exact statement, and that the confirmation token is used in step 2 with the same answers. This clarifies when the optional confirmation parameter becomes required.

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 action ('Submits an enquiry to Void Clearance Quotes') and clearly distinguishes it from a purchase and a guaranteed quote. It also separates this submission tool from the sibling informational tools (enquiry_describe, enquiry_fields) by making the action and resource explicit.

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 explicit step-by-step usage: step 1 requires answers and consent, step 2 requires the confirmation token only after person approval. It does not explicitly compare against enquiry_describe or enquiry_fields, but the workflow guidance is clear and unambiguous.

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 distinct role: enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry performs the submission. There is no overlap or ambiguity between them.

Naming Consistency4/5

Names are all lowercase snake_case and clearly related, but the pattern varies slightly: enquiry_describe is noun-verb, enquiry_fields is noun-noun, and submit_enquiry is verb-noun. Despite this minor inconsistency, the naming is predictable and readable.

Tool Count5/5

Three tools are exactly right for the narrow purpose of submitting an enquiry: one to explain, one to describe the fields, and one to perform the action. No unnecessary tools and no missing essential steps.

Completeness5/5

The tool set fully covers the enquiry submission lifecycle: understanding the process, retrieving the required fields, and submitting with a two-step confirmation flow. There are no obvious gaps for the stated domain.

Resources