Skip to main content
Glama
Sign In

site

by uk.co.varicoseveintreatmentcost
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Varicose Vein Treatment Cost — 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: "Send my enquiry to Varicose Vein Treatment Cost. I'll be emailed the names of up to three private hospitals and clinics that could help, and choose which of them, if any, receive it; nothing goes to any of them until I do. The ones I choose may pay a fixed fee for the enquiry, never a share of what I pay them."

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: Send my enquiry to Varicose Vein Treatment Cost. I'll be emailed the names of up to three private hospitals and clinics that could help, and choose which of them, if any, receive it; nothing goes to any of them until I do. The ones I choose may pay a fixed fee for the enquiry, never a share of what I pay them.
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 private hospitals and clinics, chosen by Varicose Vein Treatment Cost, 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: Send my enquiry to Varicose Vein Treatment Cost. I'll be emailed the names of up to three private hospitals and clinics that could help, and choose which of them, if any, receive it; nothing goes to any of them until I do. The ones I choose may pay a fixed fee for the enquiry, never a share of what I pay them."
  2. 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 private vein clinics and hospitals, chosen by Varicose Vein Treatment Cost, 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: Send my contact details to up to three private hospitals and clinics, chosen by Varicose Vein Treatment Cost, 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. 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 private vein clinics and hospitals, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three private vein clinics and hospitals, chosen by Varicose Vein Treatment Cost, 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."
  4. First observed

TDQS

A4.6/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 so well: it discloses validation behavior, what step 1 returns (summary, consent line, token), and the critical downstream trait that the person must click an emailed link before any provider sees the enquiry. It does not cover rate limits, failure modes, or token expiry, which keeps it just short of a 5.

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 most important fact — that this is not a purchase — is front-loaded, and the two steps are ordered clearly. The main deduction is the full consent text quoted verbatim, which duplicates the consent parameter's schema description and adds bulk without new information.

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 mutating, multi-step, human-in-the-loop tool with no output schema, the description covers the inputs, the return of step 1, the gating condition, and the email verification consequence. An agent has everything needed to run both calls correctly and safely.

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 true together with the answers, and 'confirmation' is the token returned by step 1 after human approval. That sequencing context is not derivable from the schema alone.

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?

A specific verb+resource ('Submits an enquiry') immediately disambiguated from what it is not ('NOT a purchase, NOT a guaranteed quote') and tied to the named target 'Varicose Vein Treatment Cost'. An agent can tell exactly what this does and that it is distinct from the sibling read tools enquiry_fields and enquiry_describe.

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 with explicit conditions: step 1 with answers + consent=true to validate, step 2 'only if the person agrees' with the token. It names the dependency on enquiry_fields for field keys and states the human confirmation gate, leaving nothing to inference.

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