Skip to main content
Glama

Submit an ENQUIRY to SEO company for small business (two steps; not a purchase)

submit_enquiry

Submits an enquiry to SEO company for small business: 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 company for small business 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.6/5.0
Behavior4/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 most of it: it discloses that step 1 performs validation only, that step 2 sends an email requiring a click before the team sees the enquiry, and it quotes the exact consent wording. The only gap is the failure mode (what happens on invalid answers or a stale/incorrect token) and whether calling step 2 twice resubmits.

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?

Nearly every clause earns its place—the negations, the two steps, the token, and the consent text all prevent real errors. However, it is delivered as one long unbroken block, so the two-step flow and the quoted consent sentence would be easier to parse if separated or listed.

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 mutation-style tool with nested free-form answers, no annotations, and no output schema, the description covers the pre-call prerequisite (enquiry_fields), both call shapes, what each call returns in prose, and the downstream confirmation-email gate. Nothing an agent needs in order to invoke this 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; the description earns extra by explaining that `answers` must be keyed by the field keys from enquiry_fields, that consent=true has a specific meaning (quoted verbatim), and that `confirmation` comes from step 1 and is only used on the second call. That sequencing meaning is not visible in the schema itself.

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 opens with a specific verb+resource ("Submits an enquiry to SEO company for small business") and immediately rules out the two most likely misreadings ("NOT a purchase, NOT a guaranteed quote"). It also points to the sibling tool that supplies the answer keys ("keyed by field key from enquiry_fields"), so an agent can tell what this tool does and where its inputs come from without opening any 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 with a hard gate: step 1 validates and returns a summary plus token, step 2 happens "only if the person agrees." It states not only when to call but when not to proceed, and what must be shown to the person between calls.

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