Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Drivers' Hours Calculator: 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 relevant transport compliance consultants, chosen by Drivers' Hours Calculator, 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 relevant transport compliance consultants, chosen by Drivers' Hours Calculator, 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: Happy for my details to go to a relevant transport compliance consultant, who'll get in touch with me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant transport compliance consultants, chosen by Drivers' Hours Calculator, 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
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the call validates rather than submits on step 1, that it returns a summary, consent line and token, and that submission only happens on step 2 with that token. It further explains downstream behavior an agent could not guess — an email link must be clicked before any provider sees the enquiry, and details go to up to three consultants with the ability to stop further sharing.

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 purpose and the NOT-a-purchase caveat, then cleanly split into Step 1 / Step 2, which matches how the agent must call it. The quoted consent wording is repeated verbatim from the schema and lengthens the definition without adding new information.

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 describing what each call returns (summary, consent line, token, then submission plus a confirmation email). For a nested-object, gated, two-phase tool this covers everything an agent needs to invoke it correctly and in the right order.

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, but the description adds sequencing meaning the schema cannot express: answers must be keyed by enquiry_fields keys, consent must be true on both calls, and confirmation is required only in step 2 with the token from step 1. That step-to-parameter mapping is genuinely additive, though the verbatim consent text duplicates the schema's own consent description.

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 Drivers' Hours Calculator') and immediately bounds it with 'NOT a purchase, NOT a guaranteed quote'. It also names the sibling that supplies the keys ('field key from enquiry_fields'), so an agent can distinguish it from enquiry_fields/calculate without opening a schema.

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?

Gives an explicit two-step protocol with a gating condition ('only if the person agrees') and a pre-call requirement (answers keyed from enquiry_fields, consent=true). It does not explicitly say when to route to calculate or calculator_describe instead, so the alternative-routing half of the guidance is missing.

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