Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to SEO Cornwall: 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 Cornwall 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 exist, so the description carries the full burden and does so: it states that step 1 validates rather than submits, what step 1 returns (summary, consent line, token), that step 2 triggers an email with a link the person must click before the SEO Cornwall team sees it, and the exact consent text being agreed to. The double-opt-in and non-committal nature of the action are disclosed up front, which is exactly the behaviour an agent needs before invoking a write operation.

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 1 are front-loaded in the first sentences, and every sentence carries operational content. It is slightly dense and repeats the consent wording (once inline, once quoted), which is small redundancy in an otherwise tight 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?

For a three-parameter nested-object tool with no output schema and no annotations, the description covers the full call lifecycle: prerequisites, both call shapes, what each step returns, and the downstream email-link consequence. Nothing an agent needs in order to call it 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, but the description adds real meaning: answers must be keyed by field key from enquiry_fields, and confirmation is only supplied in step 2 after human approval. That sequencing context is genuinely beyond what the schema tells you, though the format of the token itself is not described.

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 gives a specific verb+resource ("Submits an enquiry to SEO Cornwall") and immediately fences off the two most likely misinterpretations ("NOT a purchase, NOT a guaranteed quote"). It also names the sibling dependency enquiry_fields as the source of answer keys, so the agent can place this tool relative to its neighbours 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 spells out a literal when-to-call sequence: step 1 with answers plus consent=true, then step 2 only "if the person agrees" and only with the returned confirmation token. The gating condition and the ordering are both explicit, leaving nothing 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