Skip to main content
Glama

site

by uk.co.comparemyconveyancing

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

submit_enquiry

Submits an enquiry to Compare My Conveyancing — 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 conveyancing firms, who'll contact 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 conveyancing firms, who'll contact 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, the description carries the full burden and does so thoroughly. It discloses validation behavior, return of summary/consent line/token, the required second confirmation step, email sending, and the crucial condition that a link must be clicked before any provider sees the enquiry.

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 dense but not bloated; every sentence adds necessary operational detail. It is front-loaded with the core purpose and non-purpose, then proceeds logically through step 1 and step 2. The exact consent wording is included because it is essential for correct use.

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 complex two-step submission tool with no annotations and no output schema, the description is remarkably complete. It explains what the tool returns, when to call it again, what the consent requirement is, and the post-submission email behavior. An agent has enough context to execute the workflow correctly.

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, but the description adds meaningful workflow semantics beyond the schema: 'answers' are keyed by enquiry_fields, 'consent' must be true and reflects an exact quoted agreement, and 'confirmation' is the token returned in step 1. This clarifies how the parameters relate to each other in the two-step flow.

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 Compare My Conveyancing', and immediately distinguishes itself with 'NOT a purchase, NOT a guaranteed quote'. It also clearly identifies the two-step nature in the title, making it easy to tell apart from the sibling comparison and enquiry-description tools.

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 provides an explicit two-step workflow: first call with answers and consent=true to get a summary and token, then call again with the token only if the person agrees. It also references 'enquiry_fields' as the source of field keys and states what should be shown to the user, giving clear when-to-do and when-not-to-do 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

B3.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: three expose different views of comparison data, and three support the enquiry submission flow. There is no meaningful overlap between tools, even within the compare_* group, because each returns a different granularity of information.

Naming Consistency3/5

The compare_* tools follow a consistent verb_noun pattern, but the enquiry tools mix conventions: enquiry_describe and enquiry_fields are noun-first, while submit_enquiry is verb-first. All names are readable and snake_case, but the ordering inconsistency prevents a higher score.

Tool Count5/5

Six tools is well-scoped for a comparison-and-enquiry site: three tools cover the comparison content and three cover the enquiry submission flow. Each tool earns its place without unnecessary redundancy or missing essentials.

Completeness5/5

The tool set covers the full user journey: understanding the comparison, viewing criteria and options, inspecting the full table, learning what the enquiry does, fetching form fields, and submitting with a two-step consent confirmation. There are no obvious dead ends or critical missing operations for this domain.

Resources