Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to PotterySuppliesHQ: 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 PotterySuppliesHQ team sees it. Consent means the person has read and agreed to: "By submitting you agree PotterySuppliesHQ emails you a shortlist and shares nothing else with anyone."

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: By submitting you agree PotterySuppliesHQ emails you a shortlist and shares nothing else with anyone.
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.8/5.0
Behavior5/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 so: it discloses the validation-only first call, the consent token handshake, the double opt-in email link the person must click before the team ever sees the enquiry, and the exact consent sentence being agreed to. That is precisely the behaviour an agent could otherwise get wrong (skipping the human approval gate) and it is disclosed up front.

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-loads the disambiguation first, then walks Step 1 and Step 2 in execution order, which makes it easy to follow. It is dense and slightly long, and the consent sentence appears verbatim twice (body and schema), but no sentence is truly wasted.

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 step 1 returns (summary, consent line, confirmation token) and what step 2 produces (submission plus a verification email the recipient must click). For a 3-parameter, two-phase mutation with a human-in-the-loop, nothing an agent needs before calling 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; the description still adds real meaning by tying answers to "field key from enquiry_fields" (where to obtain the keys) and by constraining step 2 to "the same answers" plus the step-1 token. Minor gaps remain, such as what happens if answers are rejected in step 1 or how long the token stays valid.

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 PotterySuppliesHQ") and immediately delimits what it is not ("NOT a purchase, NOT a guaranteed quote"). It also names the companion tool enquiry_fields as the source of field keys, so an agent can tell it apart from the read-only enquiry_* siblings.

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 an explicit two-step procedure: step 1 always with consent=true to validate, step 2 only "if the person agrees" and only with the returned confirmation token. The gate condition and the ordering are stated, not inferred, and the prohibition on treating it as a purchase/quote blocks the most likely misuse.

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