Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Machinery Repair 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 relevant machinery repair specialists, chosen by Machinery Repair 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 relevant machinery repair specialists, chosen by Machinery Repair 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 relevant machinery repair specialists, who'll quote me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant machinery repair specialists, chosen by Machinery Repair 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.8/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 validation behavior, the returned summary/consent line/confirmation token, that submission triggers a double opt-in email the person must click before any provider sees the enquiry, and that details go to up to three providers with the ability to stop further sharing. That is unusually rich behavioral context for a mutation tool.

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?

It is front-loaded with the negative framing, then cleanly split into Step 1 and Step 2, so the structure aids scanning. It loses a point for restating the full consent sentence verbatim, which already appears in the schema's consent property description.

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, yet the description explains what each call returns (summary, consent line, confirmation token) and what happens downstream (verification email, provider distribution). For a nested-object, multi-step submission tool this covers everything an agent needs to call it correctly.

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 real meaning: 'answers' must be keyed by field key from enquiry_fields, and 'confirmation' is explicitly the step-1 token used only on the second call after approval. The lifecycle relationship between the step-1 return value and the step-2 parameter is not derivable from the schema alone.

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 names a specific verb and resource ('Submits an enquiry to Machinery Repair Quotes') and immediately bounds scope with 'NOT a purchase, NOT a guaranteed quote'. It also ties itself to the sibling 'enquiry_fields' as the source of field keys, so an agent can place it in the workflow 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?

It gives an explicit two-step protocol: step 1 with answers plus consent=true to validate and obtain a token, step 2 only after the person agrees. The gating condition ('only if the person agrees') and the show-the-summary obligation are stated outright, leaving nothing to inference.

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