Skip to main content
Glama

Submit an ENQUIRY to SEO for dentists (two steps; not a purchase)

submit_enquiry

Submits an enquiry to SEO for dentists: 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 SEO for dentists 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.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 behavioral burden and does so well: it discloses the validation-then-submit flow, the confirmation token, the double-submit guard, and the non-obvious downstream fact that the recipient must click an emailed link before the team sees the enquiry. It also spells out exactly what consent attests to, which is the highest-risk part of the call.

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 critical disclaimers and step structure are front-loaded in the first two sentences, and the step markers make it scannable despite being a single dense block. The closing consent quotation largely restates the schema's consent description, and the paragraph would read better split into discrete sentences per step.

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 3-parameter, nested-object tool with no output schema, the description covers everything an agent needs: ordering, the token source, the user-facing pause, and the consent semantics. The only thing it does not describe is the shape of the step-1 summary, but it explicitly tells the agent to relay it verbatim rather than interpret it, so that gap is harmless.

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, and the description earns an extra point by adding meaning the schema cannot: 'answers' are keyed by field key from enquiry_fields, and 'confirmation' is only supplied on the second call after the person approves the summary. That sequencing context turns a flat string parameter into a conditional one.

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 SEO for dentists') and immediately negates the two most likely misreadings ('NOT a purchase, NOT a guaranteed quote'), which lets an agent distinguish it from siblings like enquiry_fields. The purpose is unambiguous before any schema is opened.

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 protocol with the precondition for each call: step 1 with answers and consent=true, step 2 'only if the person agrees' with the confirmation token from step 1. It also names the point at which the agent must pause and show the person the summary and consent line, so the sequencing decision is fully specified.

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