Skip to main content
Glama

site

by uk.co.dampsurveyprices

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

submit_enquiry

Submits an enquiry to Damp Survey Prices — 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 relevant independent damp surveyors, 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 relevant independent damp surveyors, 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

A5/5.0
Behavior5/5

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

With no annotations, the description fully carries behavior disclosure. It explains validation, the returned confirmation token, the email notification, the click requirement, and the exact meaning of consent, including the quoted consent line. This gives the agent a realistic model of side effects and prerequisites.

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 long but every sentence earns its place: it front-loads the non-purchase/non-quote caveat, then structures the two steps clearly. The consent line is quoted verbatim, which avoids ambiguity. No filler or repetition.

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 two-step complexity, no output schema, and no annotations, this description is unusually complete. It tells the agent what to send, what to show the person, what to expect back, when to call again, and what happens after submission. The only implicit dependency is enquiry_fields, which is explicitly named.

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?

Although schema coverage is 100%, the description adds essential flow-level meaning: confirmation is the step-1 token that enables step-2 submission, consent has an exact quoted text, and answers must be keyed by field key from enquiry_fields. This is significant value beyond the schema's property descriptions.

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 verb and resource — 'Submits an enquiry to Damp Survey Prices' — and immediately distinguishes it from a purchase and a guaranteed quote. It also ties to the sibling tool enquiry_fields, making its role in the workflow unambiguous.

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 two-step procedure is spelled out explicitly: first call validates and returns a summary/consent line/token, second call is only for after the person agrees and includes the token. It also states that a click on the email link is required before providers see the enquiry, giving clear when-to-proceed conditions.

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: one describes the service, one provides the form schema, and one submits the enquiry. There is no overlap or ambiguity in their purposes.

Naming Consistency4/5

Two tools follow an enquiry_ prefix pattern while the third uses verb-first naming, which is a minor deviation. Overall the names are still readable and predictable within the small set.

Tool Count5/5

Three tools are exactly right for this focused domain: describing the process, fetching the field definitions, and submitting the enquiry. The scope is tight and nothing feels extraneous.

Completeness5/5

The tool set fully supports the enquiry workflow: understand the service, get the required fields, and submit with a two-step confirmation. There are no obvious dead ends or missing operations for the stated purpose.

Resources