Skip to main content
Glama

site

by uk.co.commercialepccost

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

submit_enquiry

Submits an enquiry to Commercial EPC 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 relevant commercial energy assessors, 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 commercial energy assessors, 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.7/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 burden and does so thoroughly. It discloses that the first call only validates, that the second call actually submits, that the person receives an email with a click link before any provider sees the enquiry, and includes the exact consent statement.

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 most important caveat (not a purchase, not a quote) and then logically walks through step 1 and step 2. Every sentence carries necessary behavioral or workflow information without padding.

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 two-step interaction model, the absence of an output schema, and the human-provider side effects, the description is complete. It explains what each call returns, what the confirmation token is for, and the condition under which the enquiry is actually submitted.

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%, but the description adds important workflow meaning: answers must be keyed by field key from enquiry_fields, consent must reflect the quoted statement, and confirmation is the token returned by step 1. This goes beyond the schema's basic type 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: submitting an enquiry to Commercial EPC Cost. It also explicitly distinguishes the action from a purchase and a guaranteed quote, and the two-step nature is clear from the first line 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 description gives explicit step-by-step guidance: call first with answers and consent to get a summary and token, then call again with the token only after the person agrees. It also states the tool is not for purchases, though it does not name sibling alternatives or contrast them directly.

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 clearly distinct role: enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry performs the submission. No two tools overlap in purpose, so an agent should be able to select the right one without ambiguity.

Naming Consistency3/5

All names are lowercase snake_case and share the 'enquiry' domain, but the pattern is mixed: enquiry_describe and enquiry_fields place the noun first, while submit_enquiry places the verb first. The naming is readable but not as consistent as a uniform verb_noun convention.

Tool Count5/5

Three tools is an appropriate scope for a single enquiry-submission workflow: one to orient, one to define the fields, and one to submit. Each tool earns its place without unnecessary redundancy.

Completeness5/5

The tool set covers the full enquiry lifecycle from understanding the process and schema to two-step submission with consent confirmation. There are no obvious missing operations for the narrow commercial EPC cost enquiry domain.

Resources