Skip to main content
Glama
Sign In

site

by com.brokervsadvisor
OverviewDiscussionsAdmin

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Broker vs Advisor — 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 any provider sees it. Consent means the person has read and agreed to: "Your enquiry goes only to the team behind this site, who'll contact you directly. It is not passed to any broker or adviser."

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: Your enquiry goes only to the team behind this site, who'll contact you directly. It is not passed to any broker or adviser.
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 brokers and M&A advisers, chosen by Broker vs Advisor, 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: Your enquiry goes only to the team behind this site, who'll contact you directly. It is not passed to any broker or adviser."
  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 business brokers and M&A advisers, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three business brokers and M&A advisers, chosen by Broker vs Advisor, 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.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: it discloses that step 1 is non-committal validation, that step 2 triggers a double opt-in email requiring a click before any provider sees the enquiry, and it quotes the exact consent text. Reversibility of consent, the gating side effect, and the delivery path are all surfaced.

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 the negation, then ordered by step, which suits a two-phase flow. It is dense and somewhat long — the consent string is reproduced verbatim and duplicated in the schema — but nearly every clause carries operational weight.

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?

There is no output schema, and the description compensates by describing what step 1 returns (summary, consent line, confirmation token) and what step 2 causes (submission plus a verification email). For a nested-object, consent-sensitive, two-call tool, nothing an agent needs to invoke 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 adds real value by tying each parameter to a workflow stage — answers keyed by enquiry_fields keys, consent=true required in both calls, and confirmation as the step-1 token used only in step 2. The added framing is about sequencing rather than value formats, so it lands just above baseline.

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 Broker vs Advisor") and immediately bounds it with explicit negations ("NOT a purchase, NOT a guaranteed quote"). It also anchors itself to the sibling tool enquiry_fields by naming the field-key source, so the agent can place it in the toolset without opening a 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 a precise two-step protocol: call once with answers + consent to validate and get a token, then call again with the same payload plus the token only "if the person agrees." It states both the when and the gate condition (human approval), leaving no inference about sequencing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources