Skip to main content
Glama

site

by uk.co.hvacmaintenancecost

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

submit_enquiry

Submits an enquiry to HVAC Maintenance 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 HVAC maintenance providers, 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 HVAC maintenance providers, 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.2/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that this is not a purchase, not a guaranteed quote, that the enquiry is only sent after explicit consent, that a confirmation token is required, and that the provider only sees it after the person clicks the emailed link.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but dense, with each sentence covering an essential part of the two-step flow or a critical caveat. It is front-loaded with the most important 'not a purchase' distinction, though some phrasing overlaps with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully explains the two-step process, consent requirements, the confirmation token, and the email-link step. It even includes the exact consent wording. The main gap is that it doesn't describe what a successful step-2 call returns, and there is no output schema to fill that gap.

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 schema already documents all three parameters. The description adds meaningful context by explaining that answers come from enquiry_fields, that confirmation is the token returned in step 1, and that consent must match a specific consent line, linking the parameters to the workflow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool submits an enquiry to HVAC Maintenance Cost and explicitly distinguishes it from a purchase or guaranteed quote. However, it does not explicitly compare itself to sibling tools enquiry_describe and enquiry_fields, so sibling differentiation relies mostly on the tool name and title.

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 two-step calling sequence is described in detail: first call validates and returns a token, second call submits only after the person agrees. It also references enquiry_fields for answer keys, implying a prerequisite, but it does not explicitly state when to choose this tool over enquiry_describe or enquiry_fields.

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

Each tool has a distinct role: enquiry_describe explains the process, enquiry_fields provides the form schema, and submit_enquiry performs the submission. There is no meaningful overlap, and the descriptions reinforce when each should be used.

Naming Consistency3/5

The names share a clear topical connection to 'enquiry', but the pattern is mixed: submit_enquiry follows verb_noun, while enquiry_describe and enquiry_fields lead with the noun. The names are readable, but the convention is not fully consistent.

Tool Count5/5

Three tools is exactly right for this narrow workflow: one to orient the agent, one to supply the schema, and one to handle submission. Each tool has a clear purpose and none feel redundant.

Completeness5/5

The tool set fully covers the enquiry lifecycle described: understanding the process, retrieving required fields, and submitting with consent confirmation. There are no obvious dead ends, and the two-step confirmation is handled within submit_enquiry itself.

Resources