Skip to main content
Glama

Submit an ENQUIRY to PPC agency Bristol (two steps; not a purchase)

submit_enquiry

Submits an enquiry to PPC agency Bristol: 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 PPC agency Bristol 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 burden well: it discloses that step 1 is non-committal and returns a summary, consent line and token, that step 2 actually submits, and that delivery is gated by a double opt-in email link before the agency sees anything. It also spells out exactly what consent means, which is a genuine behavioral contract an agent cannot infer from the schema.

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?

It is a single dense paragraph, but the most important constraint ('NOT a purchase, NOT a guaranteed quote') is front-loaded and the step numbering makes the sequence easy to scan. The verbatim consent sentence is slightly redundant with the schema's consent description, costing a point.

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, and the description compensates by enumerating what each step returns (summary, consent line, token; then an email with a confirmation link). Given the nested answers object and the two-phase submission, nothing an agent needs in order to call this 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; the description earns more by linking `answers` to field keys from enquiry_fields and explaining that `confirmation` is the token returned by step 1 used only after approval. Some of this overlaps the schema's own parameter descriptions, so it is additive rather than transformative.

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 (submit an enquiry to PPC agency Bristol) and immediately bounds the scope with 'NOT a purchase, NOT a guaranteed quote'. A negative scope plus a concrete action lets an agent tell this apart from the read-only siblings enquiry_fields and enquiry_describe without opening 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-call procedure: step 1 with answers and consent=true to validate, step 2 only 'if the person agrees' with the same answers plus the token. It even states the human-in-the-loop requirement (show the summary and consent line) and points at enquiry_fields as the source of field keys, so the correct sequence is unambiguous.

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