Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Copywriting for SEO: 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 Copywriting for SEO 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?

No annotations are provided, so the description carries the full disclosure burden and does so: validation behavior, what step 1 returns (summary, consent line, token), the exact consent wording, and the crucial downstream effect that the team only sees the enquiry after the person clicks the emailed link. This is behavior an agent could not infer from the schema and prevents a premature submission.

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?

Content is front-loaded and every element earns its place, including the quoted consent sentence, which is required verbatim. It is delivered as one dense run-on block rather than separated Step 1/Step 2 lines, which slightly hurts scanability and prevents a 5.

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 two-phase tool with a free-form nested answers object and no output schema, the description supplies everything an agent needs: required inputs per phase, what each phase returns, the consent contract, and the post-submission email confirmation step. Nothing consequential is left to inference.

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 baseline is 3; the description earns above that by explaining that answers are keyed by field key from enquiry_fields, spelling out consent's exact meaning, and clarifying that confirmation is the step-1 token used only on the second call (the schema marks it optional without saying why). Token expiry or error handling is not covered, keeping it at 4.

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 and resource ("Submits an enquiry to Copywriting for SEO") and immediately disambiguates intent with "NOT a purchase, NOT a guaranteed quote." It also names the field source (enquiry_fields), which distinguishes it from the sibling lookup tools without needing their schemas.

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 with consent=true to validate, then step 2 "only if the person agrees." It also states the alternative/eligibility condition (consent meaning) so the agent knows when calling is appropriate and when it is not.

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