Skip to main content
Glama

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Tide Times Compare: 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 any provider sees it. Consent means the person has read and agreed to: "By submitting you agree Tide Times Compare shares your details with the providers who quote."

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: By submitting you agree Tide Times Compare shares your details with the providers who quote.
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 it well: it discloses validation behavior, the returned summary/consent line/token, the double opt-in email with a click-through link before any provider sees the data, and the exact consent wording. The main remaining gap is failure/error behavior, which is minor against the disclosure of side effects and data flow.

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 and structured as two labelled steps, which suits a multi-call flow. It is on the long side and quotes the consent sentence twice (once in the flow, once in the trailing consent definition), a redundancy that could be trimmed.

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 mutating, person-facing workflow with no output schema and no annotations, the description covers validation, return values, the confirmation handshake, downstream email verification and the exact consent semantics. An agent has everything needed to execute both calls correctly and safely.

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, but the description adds real meaning the schema cannot: it explains that `confirmation` is the token returned in step 1 and is only passed on the second call, and that `consent` gates both calls. It does not explain how to obtain field keys beyond pointing at enquiry_fields, but the sequencing semantics are well covered.

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 names a specific verb and resource ("Submits an enquiry to Tide Times Compare") and immediately disambiguates intent with "NOT a purchase, NOT a guaranteed quote." It also names the sibling enquiry_fields as the source of the field keys, so an agent can distinguish and chain to the right tool.

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 two-step protocol with conditions: step 1 with answers + consent=true, then step 2 "only if the person agrees" with the same answers plus the confirmation token. The when-not condition (do not submit without the person's approval) is stated, and the prerequisite tool (enquiry_fields) is named.

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