Skip to main content
Glama

site

by uk.co.cctvdrainsurveycost

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

submit_enquiry

Submits an enquiry to CCTV Drain Survey 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 local CCTV drain survey engineers, 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 local CCTV drain survey engineers, 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.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It fully discloses the two-step validation flow, the need for consent, the confirmation token, the email-link requirement, and the fact that providers see nothing until the person clicks the link.

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 detailed but every sentence earns its place. It front-loads the most critical caveats and organizes the two steps clearly, making the complex flow digestible without 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?

Despite having no output schema, the description covers what step 1 returns, what step 2 requires, what happens after submission, and the exact consent wording. This is complete enough for an agent to execute the flow correctly.

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?

Schema coverage is 100%, but the description adds significant workflow meaning beyond the schema: answers must be keyed by field keys from enquiry_fields, consent must be true and represent specific agreed language, and confirmation is the step-1 token only used after approval.

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?

States a clear verb and resource: submits an enquiry to human providers. The description explicitly distinguishes this from a purchase and a guaranteed quote, and the two-step nature is front-loaded in the title and description.

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?

Provides clear procedural context: when to call step 1, when to call step 2, and the condition that gates step 2. It implies use after collecting answers from enquiry_fields, though it does not explicitly name sibling output as prerequisites or state when not to use the tool.

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

Each tool has a clearly distinct role: enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry executes the submission. There is no overlap or ambiguity between them.

Naming Consistency4/5

All tools clearly reference 'enquiry', but word order varies: enquiry_describe and enquiry_fields put 'enquiry' first, while submit_enquiry puts it last. This is a minor deviation from a fully consistent verb_noun pattern.

Tool Count5/5

Three tools is well-scoped for a focused enquiry submission flow: one to understand the process, one to provide fields, and one to submit. Each tool earns its place and there is no bloat.

Completeness5/5

The tool set covers the entire enquiry lifecycle, from explanation and field schema to submission with a two-step confirmation. No obvious gaps exist for the stated purpose.

Resources