Skip to main content
Glama
Sign In

site

by uk.co.privatesurgerycosts
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Private Surgery Costs — 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 Private Surgery Costs. I'll be emailed the names of up to three relevant 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 Private Surgery Costs. I'll be emailed the names of up to three relevant 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 relevant private hospitals and clinics, chosen by Private Surgery Costs, 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 Private Surgery Costs. I'll be emailed the names of up to three relevant 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: Happy for my details to go to relevant private hospitals and clinics, who'll contact me directly about costs."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant private hospitals and clinics, chosen by Private Surgery Costs, 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 provided, the description carries the full burden and does so well: it discloses validation, the returned summary/consent line/token, the requirement to show the summary, the second submission step, and the email-link gate before providers can see the enquiry.

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 two-step structure is clear and front-loaded with the key non-purchase caveat. It is somewhat long because it repeats the full consent text already present in the schema, but that repetition supports correct consent handling.

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 submission tool with no annotations and no output schema, the description is complete: it explains both calls, required inputs, returned values, consent handling, and the email confirmation gate before providers see the enquiry.

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 schema already documents all three parameters. The description still adds workflow meaning by explaining that answers are keyed by enquiry_fields, consent must be true, and the confirmation token comes from Step 1 after the person approves the summary.

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 Private Surgery Costs. It immediately clarifies scope with 'NOT a purchase, NOT a guaranteed quote,' so the agent can distinguish this from a purchasing or quoting tool.

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 gives explicit two-step usage: Step 1 validates and returns a summary/token, and Step 2 is called only if the person agrees. It also states that answers are keyed by field key from enquiry_fields, connecting the workflow to the relevant sibling tool.

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