Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to SEO services Glasgow: 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 services Glasgow 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.5/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 only validates, what step 1 returns (summary, consent line, token), that submission triggers a double opt-in email whose link must be clicked before the team sees anything, and the exact consent wording. Gaps remain around failure modes — expired or reused tokens, re-submission of the same person, and whether step 1 persists data — which matter for a two-phase write.

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 purpose and the two negations, then proceeds in step order, which mirrors how the agent must call it. Slight redundancy: the consent statement is quoted in the description and again in the schema, and the step-2 call arguments restate step-1 arguments in full. Still dense with substance rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers complexity well for a nested-object, two-phase tool with no output schema: it describes what step 1 returns and what the person receives on step 2, so return values need no separate schema. What is missing is error/edge behavior (invalid answers, token mismatch) that an agent would need to recover mid-flow.

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 would be 3, but the description adds workflow meaning the schema cannot: 'answers' are keyed by field keys obtained from enquiry_fields, 'consent' is a person-confirmed attestation with fixed wording, and 'confirmation' is only supplied in step 2 after approval. That sequencing constraint is genuine added value.

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 services Glasgow') and immediately bounds it with two negations ('NOT a purchase, NOT a guaranteed quote'). The two-step structure is spelled out, so an agent can tell exactly what this does versus the read-only siblings enquiry_fields and enquiry_describe, which are referenced as the source of 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?

Explicit ordering and gating conditions: step 1 with answers + consent=true to validate, step 2 'only if the person agrees' with the same answers plus the token. It also states the human-facing obligation (show the summary and consent line) and forbids the implicit alternative of submitting in one shot. Little is left 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