Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Abnormal Load Quotes: 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 abnormal load and heavy haulage operators, chosen by Abnormal Load Quotes, 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 abnormal load and heavy haulage operators, chosen by Abnormal Load Quotes, 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 abnormal load and heavy haulage operators, who'll quote the move directly."New value: +"true only when the person has agreed to: Send my contact details to up to three abnormal load and heavy haulage operators, chosen by Abnormal Load Quotes, 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.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden and it does well: it discloses validation on step 1, the returned summary/consent line/token, the external side effect (email to the person requiring a click), that up to three providers then see the details, and that the person can stop further sharing. It does not cover what happens on an invalid token, whether repeating step 2 double-submits, or any error/retry behavior for a mutation with real-world consequences.

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 scope negation, then step 1 and step 2 in order — easy for an agent to follow. The main inefficiency is the verbatim repetition of the full consent paragraph, which the schema already defines for the consent parameter.

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?

For a two-phase mutation tool with no annotations and no output schema, the description supplies the flow, the intermediate return values, the consent semantics and the downstream effect, which is nearly everything an agent needs. The remaining gap is failure and idempotency guidance for re-invoking step 2 or handling an expired token.

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 baseline is 3, but the description adds real meaning: 'answers' must be keyed by field key from enquiry_fields, consent must mean the specific quoted agreement, and 'confirmation' is the token from step 1 used only after the person approves the summary. That maps each parameter to a workflow position rather than restating the schema.

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 Abnormal Load Quotes') and immediately bounds scope with 'NOT a purchase, NOT a guaranteed quote'. The two-step framing and the email-confirmation gate make it unmistakable against the read-only siblings enquiry_fields and enquiry_describe.

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 explicit sequencing: call step 1 with answers and consent=true, show the person the summary and consent line, then call step 2 with the same answers plus the confirmation token 'only if the person agrees'. Prerequisites (consent agreement, token from step 1) and the alternative action (stop after step 1) are both spelled out.

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