Skip to main content
Glama
Sign In

site

by uk.co.cataractsurgerycost
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Cataract Surgery 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 Cataract Surgery 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."

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my enquiry to Cataract Surgery 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 Cataract Surgery 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 Cataract Surgery 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 eye clinics and hospitals, chosen by Cataract Surgery 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 Cataract Surgery 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 eye 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 eye clinics and hospitals, chosen by Cataract Surgery 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.9/5.0
Behavior5/5

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

Since there are no annotations, the description carries the full burden and excels. It reveals key behavioral aspects not in the schema, such as the definition of 'consent' terms, the resulting email process, and the necessity of a confirmation token linking the two steps.

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?

While the description is long, its length is entirely justified by the complexity of the business process. The information is highly structured using 'Step 1' and 'Step 2' to maintain readability and flow.

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?

It is highly complete for a complex, multi-stage tool. It covers the initiation of the request, the required user consent/action, the token mechanism for follow-up, and the legal disclaimers.

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?

The description adds crucial semantic value to every parameter. It explains that 'answers' must be keyed by 'enquiry_fields,' defines 'confirmation' as the 'token from step 1,' and provides the full legal text for the 'consent' parameter.

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 purpose is immediately clear: to submit an enquiry. It explicitly warns the user that it is not a purchase or a guaranteed quote, distinguishing its function from transactional tools.

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 description functions as an operational manual, detailing a strict two-step workflow (Step 1 and Step 2). This explicit guidance on sequence and conditions (getting the token) is the highest level of usage clarity possible.

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