Skip to main content
Glama

Submit an ENQUIRY to SEO content marketing (two steps; not a purchase)

submit_enquiry

Submits an enquiry to SEO content marketing: 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 content marketing 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 burden and does so: it discloses that step 1 is a validation pass returning a summary, consent line and token, that submission only occurs on step 2, that a double opt-in email must be clicked before the team sees the enquiry, and what consent means. Side effects and gating conditions are unusually well surfaced.

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-loaded with the critical "NOT a purchase" framing and then structured as Step 1 / Step 2, which matches how the agent must call it. The verbatim restatement of the consent sentence duplicates the schema's consent description, a minor redundancy in an otherwise dense and purposeful block.

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, so the description must explain returns, and it does: step 1 yields a summary, consent line and confirmation token; step 2 triggers an email with a click-through link. For a two-phase, consent-sensitive, non-idempotent submission tool, an agent has everything needed to call it correctly and to instruct the end user.

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 real meaning: answers must be keyed by field key obtained from enquiry_fields, consent must be true in both steps, and confirmation is the token from step 1 supplied only after the person approves the summary. The ordering relationship between the parameters is not expressible in the schema and is captured here.

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 content marketing") and immediately bounds it with "NOT a purchase, NOT a guaranteed quote," which prevents the most likely misread. It also distinguishes itself from the sibling enquiry_fields by naming it as the source of the field keys.

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: step 1 with answers plus consent=true to validate, step 2 "only if the person agrees" with the token added. It also states the negative conditions (not a purchase, not a guaranteed quote) and points at enquiry_fields for obtaining keys, leaving nothing about sequencing to inference.

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