Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Racking Inspection 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: "Send my contact details to up to three racking and mezzanine floor firms, chosen by Racking Inspection Cost, 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 racking and mezzanine floor firms, chosen by Racking Inspection Cost, 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: Send my contact details to up to three rack inspectors, chosen by Racking Inspection Cost, 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."New value: +"true only when the person has agreed to: Send my contact details to up to three racking and mezzanine floor firms, chosen by Racking Inspection Cost, 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. 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 SEMA approved rack inspectors, who'll quote me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three rack inspectors, chosen by Racking Inspection Cost, 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."
  3. 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, what step 1 returns (summary, consent line, confirmation token), what step 2 triggers (a double opt-in email that must be clicked before any provider sees it), and the downstream consequence that up to three named firms will contact the person directly.

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?

The step-numbered structure is front-loaded and easy to follow, with the most important constraint ('NOT a purchase') in the first clause. The full consent paragraph is reproduced verbatim even though it also appears in the schema, which is defensible for display purposes but is the one place the text stops earning every word.

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 exactly what each step returns and what the end user will receive by email. For a two-phase mutation with human-in-the-loop consent, 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, but the description adds workflow meaning the schema cannot: the same answers object must be resubmitted alongside the confirmation token in step 2, and consent is only true after the person has read and agreed to the quoted line. The only shortfall is that it never explains the accepted value types for answers (string/number/boolean), which the schema handles.

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 (submit an enquiry to human providers) and immediately bounds it with 'NOT a purchase, NOT a guaranteed quote,' which is exactly the distinction an agent needs against a transactional tool. It also anchors the answers parameter to the sibling tool ('keyed by field key from enquiry_fields'), so the relationship to enquiry_fields is unambiguous.

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 spells out a two-call protocol with explicit gating: step 1 validates and returns a summary plus token, step 2 only happens 'only if the person agrees.' The human-approval condition is stated rather than implied, which is the crucial usage rule for this tool.

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