Skip to main content
Glama
Sign In

site

by com.commercialrefinancequotes
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Commercial Refinance 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 any provider sees it. Consent means the person has read and agreed to: "By sending this you agree the Commercial Refinance Quotes team reads your enquiry and replies by email. We do not pass it to 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 Commercial Refinance Quotes team reads your enquiry and replies by email. We do not pass it to 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: Commercial Refinance Quotes shares your details with commercial lenders and brokers who may quote."New value: +"true only when the person has agreed to: By sending this you agree the Commercial Refinance Quotes team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.7/5.0
Behavior4/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 most of it: it discloses validation behavior, the returned summary/consent line/token, and the double opt-in email link that must be clicked before any provider sees the enquiry. The only gap is that it never states what a failed validation response looks like or whether retries are safe.

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 disambiguation first, then numbered steps, which matches how an agent must execute it. The consent wording is quoted twice (description body and schema), which is slight redundancy but serves the agent that never reads the nested schema.

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 three-parameter, two-call, consent-gated mutation with no annotations and no output schema, the definition covers the full lifecycle: validation call, human confirmation, token reuse, and the downstream email verification. Nothing an agent needs in order 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds real meaning: answers must be keyed by field key from enquiry_fields, consent must be literally true and semantically means the person read and agreed to the quoted line, and confirmation is the token from step 1 used only after approval. That is more than the schema conveys.

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 Commercial Refinance Quotes") and immediately delimits it with "NOT a purchase, NOT a guaranteed quote," which separates it from any transaction-style sibling. An agent can tell what this tool does 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?

Gives an explicit two-step protocol with the gating condition for step 2 ("only if the person agrees") and points to enquiry_fields as the source of field keys. It also states the action is not a purchase and not a guaranteed quote, so an agent knows not to treat a success as a completed sale.

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