Skip to main content
Glama

Submit an ENQUIRY to SEO for accountants (two steps; not a purchase)

submit_enquiry

Submits an enquiry to SEO for accountants: 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 for accountants 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?

No annotations exist, so the description carries the full behavioral burden and does so: it discloses that step 1 only validates and returns a summary/consent line/token, that the enquiry is not visible to the team until the recipient clicks an emailed link, and that no purchase or guaranteed quote occurs. Consent is defined verbatim, which is exactly the kind of consequential detail an agent must convey to a person.

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 most important disambiguation (not a purchase, not a quote), then cleanly ordered into Step 1 and Step 2. It is dense but mostly earns its length; the main redundancy is restating consent requirements both inline and as a verbatim quote, which slightly inflates the block.

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, multi-step, non-annotated mutation tool with no output schema, the description covers inputs, step sequencing, what is returned at each stage, and the downstream email-confirmation gate. Nothing an agent needs in order to call this correctly or explain it to a person 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 above baseline by explaining the process role of each parameter — answers keyed by field key from enquiry_fields, consent tied to a specific statement, and confirmation as the step-1 token used only in step 2 with identical answers. It does not add format or type detail beyond the schema, which is fine given full coverage.

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 for accountants") and immediately disambiguates intent with "NOT a purchase, NOT a guaranteed quote." The two-step framing plus the sibling field source (enquiry_fields) lets an agent distinguish this from enquiry_fields and enquiry_describe without opening any schema.

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 explicit when-to-call guidance for each step: step 1 with answers and consent=true, step 2 only after the person agrees and only with the same answers plus the confirmation token. The gating condition ("only if the person agrees") and the human-facing obligations (show the summary and consent line) are spelled out rather than implied.

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