Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Roofing Quotes UK: 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: "Send my contact details to up to three roofing and damp contractors who do the work I asked about, chosen by Roofing Quotes UK, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "answers": "<answers>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my contact details to up to three roofing and damp contractors who do the work I asked about, chosen by Roofing Quotes UK, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Roofing Quotes UK passes your details to roofing contractors covering your area."New value: +"true only when the person has agreed to: Send my contact details to up to three roofing and damp contractors who do the work I asked about, chosen by Roofing Quotes UK, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well: it discloses that step 1 is a dry validation returning a token, that step 2 triggers an email the person must click before any provider sees the data, and that details go to up to three contractors. It omits failure modes and token lifetime/expiry, which matter for a multi-step mutation.

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?

Front-loaded with the negations, then cleanly organized as Step 1 / Step 2, with no filler. The consent paragraph is reproduced almost verbatim from the `consent` parameter description, which is defensible for a person-facing consent line but is still duplicated text.

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?

There is no output schema, and the description compensates by naming what step 1 returns (summary, consent line, confirmation token) and what step 2 produces (submitted enquiry plus a verification email). For a 3-parameter nested tool with a two-phase side effect, nothing an agent needs in order to call it correctly is missing.

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; the description earns above that by explaining the sequencing contract the schema cannot express — that step 2 must repeat "the same answers" with the token produced by step 1. The answers keying is tied to the `enquiry_fields` sibling, adding cross-tool meaning beyond the schema's "keyed by field key".

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 specific verb and resource ("Submits an enquiry to Roofing Quotes UK") and immediately scopes it with two explicit negations: "NOT a purchase, NOT a guaranteed quote." It also references the `enquiry_fields` sibling as the source of field keys, so an agent can place it in the flow without opening another schema.

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?

Gives an explicit two-call protocol: step 1 with answers + consent=true to validate and obtain a token, step 2 only "if the person agrees." It also states the gating condition and what must be shown to the person between calls, leaving no inference about when each call is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources