Skip to main content
Glama

Submit an ENQUIRY to Sell My Business Quotes (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Sell My Business Quotes: 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 Sell My Business Quotes team sees it. Consent means the person has read and agreed to: "By submitting you agree your enquiry goes to Ellul Solutions Ltd (company 17364530), the business brokerage behind Sell My Business Quotes, which may contact you about it. With your agreement it may introduce you to buyers, brokers or advisers for the sale or purchase of a whole business. It introduces only: it does not give investment advice, negotiate a share sale for you, hold money or arrange finance."

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: By submitting you agree your enquiry goes to Ellul Solutions Ltd (company 17364530), the business brokerage behind Sell My Business Quotes, which may contact you about it. With your agreement it may introduce you to buyers, brokers or advisers for the sale or purchase of a whole business. It introduces only: it does not give investment advice, negotiate a share sale for you, hold money or arrange finance.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Sell My Business Quotes receives your enquiry and may contact you about it. With your agreement it may introduce you to buyers, brokers or advisers for the sale or purchase of a whole business. It introduces only: it does not give investment advice, negotiate a share sale for you, hold money or arrange finance."New value: +"true only when the person has agreed to: By submitting you agree your enquiry goes to Ellul Solutions Ltd (company 17364530), the business brokerage behind Sell My Business Quotes, which may contact you about it. With your agreement it may introduce you to buyers, brokers or advisers for the sale or purchase of a whole business. It introduces only: it does not give investment advice, negotiate a share sale for you, hold money or arrange finance."
  2. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Sell My Business Quotes shares your details with business brokers and M&A advisers who may contact you."New value: +"true only when the person has agreed to: By submitting you agree Sell My Business Quotes receives your enquiry and may contact you about it. With your agreement it may introduce you to buyers, brokers or advisers for the sale or purchase of a whole business. It introduces only: it does not give investment advice, negotiate a share sale for you, hold money or arrange finance."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden and does so: it states validation occurs, that step 1 returns a summary, consent line and token, that the enquiry is only submitted on step 2, and that the person must click an emailed link before the team sees it. It also discloses the consent scope and the broker's limits (no advice, no negotiation, no money handling).

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?

The Step 1 / Step 2 structure is front-loaded and easy to follow, but the full consent paragraph is quoted verbatim in the description and again in the schema's consent field, which is duplicated text. Trimming that quote to a reference would tighten an otherwise dense and purposeful description.

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-phase, consent-gated submission tool with no output schema and no annotations, the description covers everything needed: the flow, the returned summary and token, the double-opt-in email step, and the meaning of consent. Nothing required to call it 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 goes further by explaining that answers must be keyed by field key from enquiry_fields and that confirmation is required only on the second call with the same answers. It adds the conditional timing of the token parameter, which the schema alone does not convey.

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 opens with a specific verb and resource ('Submits an enquiry to Sell My Business Quotes') and immediately disambiguates intent with 'NOT a purchase, NOT a guaranteed quote'. It is clearly distinguishable from read-only siblings like enquiry_fields and enquiry_describe, which supply field definitions rather than submission.

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 spells out a two-step protocol with explicit conditions: call with answers and consent=true first, show the person the summary, then call again only if they agree. The gating condition ('only if the person agrees') and the required action between steps ('show the person the summary and the consent line') leave 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