Skip to main content
Glama

Submit an ENQUIRY to Link building SEO service (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Link building SEO service: 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 Link building SEO service 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 well: it discloses that the call validates rather than submits on step 1, that step 2 triggers a double opt-in email the person must click before the team sees the enquiry, and it defines consent verbatim. These are exactly the behavioral facts (destructive-looking action is actually non-binding, external visibility is delayed) an agent 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?

Front-loaded with the purpose and negation, then cleanly split into "Step 1:" and "Step 2:" segments, which matches the actual call sequence. It loses a point for mild redundancy: the consent sentence appears in full in the body and again as the schema already quotes it, and the sentences are long semicolon chains.

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, free-form `answers` object with no output schema, the description supplies the missing context: where the keys come from (enquiry_fields), what step 1 returns, and what the person will receive. Nothing needed to invoke either call correctly is absent.

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 extra by tying `answers` to field keys from the enquiry_fields sibling and by establishing that `confirmation` is only supplied on the second call and only after human approval, and that both calls use the same answers. The consent wording is largely a restatement of the schema's own description, which keeps this from a 5.

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 Link building SEO service") and immediately bounds the scope with two explicit negatives ("NOT a purchase, NOT a guaranteed quote"), which prevents the agent from treating it as a commerce action. It also implicitly routes the agent to the sibling that supplies field keys ("keyed by field key from enquiry_fields").

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 two-call procedure: step 1 with answers plus consent=true to validate, then step 2 only "if the person agrees" with the same answers plus the confirmation token. It also states the agent-side obligations (show the person the summary and the consent line) before proceeding, so when-to-call and preconditions are fully specified.

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