Skip to main content
Glama

Submit an ENQUIRY to CRM for trades (two steps; not a purchase)

submit_enquiry

Submits an enquiry to CRM for trades: 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 the CRM for trades team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."

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: Happy to be contacted about this enquiry by the company that runs this site.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that step 1 only validates and returns a summary/consent line/token, that submission happens only in step 2, and that a double opt-in email is sent before the team sees the enquiry. It does not cover validation failure behavior, error handling, or any auth/rate-limit considerations, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded paragraph that opens with the scope exclusions, then walks Step 1 and Step 2 in order. The repetition of 'consent=true' and the consent wording is justified because it is the legal basis of the call, and nothing else is padding.

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?

For a nested-object, two-phase, consent-gated submission tool with no annotations and no output schema, the description covers the shape of the step-1 return, the gating condition, the side effect of the email, and the definition of consent. An agent has enough to execute both phases correctly without further context.

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 meaning the schema cannot: 'answers' must be keyed by field key from enquiry_fields, and 'confirmation' is only supplied on the second call after the person approves the summary. This explains the sequencing relationship among the three parameters rather than just restating them.

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 CRM for trades') and immediately bounds it with negative scope ('NOT a purchase, NOT a guaranteed quote'). It also ties the tool to the sibling 'enquiry_fields' by naming it as the source of field keys, so an agent can distinguish this from the lookup tools.

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?

Usage is spelled out as an explicit two-step protocol with a gating condition: call once with answers+consent to validate, and call again 'only if the person agrees' with the confirmation token. It also states what consent means and what the person must do (click the email link) before the team sees the enquiry, leaving no ambiguity 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