Skip to main content
Glama

Submit an ENQUIRY to Tools for PPC (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Tools for PPC: 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 Tools for PPC 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: it says the tool validates rather than submits on the first call, explains what it returns (summary, consent line, confirmation token), and discloses a post-call gate where the person must click an emailed link before the Tools for PPC team sees the enquiry. It also defines consent positively, which is exactly the behavioral context a human-in-the-loop tool needs.

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?

Everything present earns its place — the negations, the two steps, and the quoted consent wording are all load-bearing. The main weakness is that the two-step workflow is delivered in long run-on sentences rather than clearly segmented, which makes it marginally harder to scan than it needs to be.

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 nested-object, two-call workflow with no output schema and no annotations, the description covers what each call returns, the ordering constraint, the consent semantics, and the downstream email-verification gate. An agent has everything needed to drive both steps correctly.

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 beyond it: answers are keyed by field keys sourced from enquiry_fields, and the confirmation token is only provisioned in step 1 and only used after the person approves the summary. That sequencing is not derivable from the schema alone, though it does not add detail on individual answer field types.

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 pairs a specific verb and resource ('Submits an enquiry to Tools for PPC') with explicit scope negations ('NOT a purchase, NOT a guaranteed quote'), so an agent cannot mistake this for a purchase or quote tool. It also names where the answer keys come from ('field key from enquiry_fields'), which distinguishes it from the sibling field-description 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?

Both steps and their preconditions are spelled out: step 1 with answers and consent=true to get a summary and token, step 2 only after the person agrees, with the same answers plus the token. It also states the human-facing obligation at each step ('show the person the summary and the consent line'), 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