Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to PPC agency Manchester: 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 Manchester 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 only validates and returns a summary/consent line/token, that step 2 actually submits, and that a double opt-in email link must be clicked before the agency sees the enquiry. It also spells out the exact consent wording, which is critical behavioral context for a submission tool.

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 key disambiguation ('NOT a purchase') and then structured as Step 1 / Step 2, which is easy to follow. It is dense and the long sentences plus the embedded consent quote add length, but nearly every clause carries operational information.

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 two-step, nested-object tool with no output schema, the description explains what each call returns (summary, consent line, token) and the end-to-end consequence (email verification before the agency sees it). Nothing an agent needs to invoke it correctly appears to be 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 are keyed by field key from enquiry_fields, consent must be true only after the person agrees, and confirmation is the token returned by step 1 used only on the second call. That clarifies the temporal dependency between parameters beyond the schema's static descriptions.

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 PPC agency Manchester') and immediately disambiguates scope with 'NOT a purchase, NOT a guaranteed quote'. The two-step nature and the relationship to enquiry_fields (answers keyed by field key) distinguish it from the sibling lookup tools.

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 when-to-use sequence: step 1 with answers and consent=true, then step 2 only if the person agrees, with the same answers plus the confirmation token. It also states the gating condition (person must approve the summary) and what consent means, leaving little 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