Skip to main content
Glama

Submit an ENQUIRY to Business Worth Calculator (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Business Worth Calculator: 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 Business Worth Calculator 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. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: Send my contact details to up to three business valuation and exit advisers, chosen by Business Worth Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."New value: +"true only when the person has agreed to: Happy to be contacted about this enquiry by the company that runs this site."
  2. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: Happy for my details to go to a relevant corporate finance adviser, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three business valuation and exit advisers, chosen by Business Worth Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With zero annotations the description carries the whole behavioral burden, and it does most of it: it discloses the dry-run/validate pattern, token issuance, the email-confirmation gate before the team sees the enquiry, and consent semantics. Gaps remain around failure modes — what happens on an invalid or expired confirmation token, or if validation rejects the answers — but the core workflow and side effects are well disclosed.

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 critical negative framing and then ordered by step, which matches execution order. The consent statement is restated at the end after appearing in step 1, and the single block is long, but no sentence is filler.

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 multi-step submission tool with a nested object, no annotations and no output schema, the description supplies the missing return information (summary, consent line, token) and the downstream effect of step 2 (email with a click-through link). An agent has enough to execute both calls 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: 'answers' are keyed by field key from enquiry_fields, 'consent' must be literally true and carries a quoted consent statement, and 'confirmation' is the token returned by step 1 and supplied only after approval. That is more than the schema states on its own.

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 Business Worth Calculator') and immediately bounds it with 'NOT a purchase, NOT a guaranteed quote', which separates it from the sibling calculate tool. An agent can identify the operation and its non-goals without opening the 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?

The two-step protocol is spelled out explicitly: step 1 validates and returns a summary, and step 2 is called 'only if the person agrees'. The gate condition for the second call is unambiguous, and the description implicitly routes field discovery to enquiry_fields by naming the field keys.

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