Skip to main content
Glama
Sign In

site

by com.insurancebyprofession
OverviewDiscussionsAdmin

Submit an ENQUIRY to Insurance by Profession (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Insurance by Profession: 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 Insurance by Profession team sees it. Consent means the person has read and agreed to: "By sending this you agree the Insurance by Profession team reads your message and replies by email. We do not pass it to an insurer, a broker or anyone else."

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 sending this you agree the Insurance by Profession team reads your message and replies by email. We do not pass it to an insurer, a broker or anyone else.
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 Insurance by Profession passes your details to an FCA-authorised insurance broker or insurer, who may contact you about cover."New value: +"true only when the person has agreed to: By sending this you agree the Insurance by Profession team reads your message and replies by email. We do not pass it to an insurer, a broker or anyone else."
  2. 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 behavioral burden and does so well: it discloses validation behavior, the returned summary/consent line/token, the email-link confirmation gate before the team sees the enquiry, and the privacy statement defining consent. This is exactly the context an agent needs to avoid treating it as a purchase or quote.

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-by-step structure is front-loaded and highly scannable; each sentence conveys a distinct requirement. It is somewhat long because the consent language is repeated verbatim, but that repetition serves the required user-facing disclosure.

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 complex two-step mutation tool with no output schema, the description explains both invocations, the intermediate return values, the final submission outcome, and the email confirmation gate. An agent would not need to inspect the schema to use it 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 already 100%, so the baseline is 3, but the description adds real meaning: 'answers' must be keyed by field key from enquiry_fields, and 'confirmation' is explicitly the token returned in step 1 after approval. The two-step gating of the token adds value beyond the schema alone, though the consent text is slightly redundant with the schema.

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 states a specific verb and resource ('Submits an enquiry to Insurance by Profession') and immediately disambiguates what it is not ('NOT a purchase, NOT a guaranteed quote'). The two-step framing further distinguishes it from any single-call sibling.

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 explicitly prescribes step 1 (submit answers plus consent=true to get a summary and token) and step 2 (resubmit with the token only after the person agrees). It also points to the sibling 'enquiry_fields' for field keys, leaving no ambiguity about when and how to call it.

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