Skip to main content
Glama
Sign In

site

by uk.co.kneereplacementcost
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Knee Replacement 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 Knee Replacement 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 Knee Replacement 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 Knee Replacement 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 Knee Replacement 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 orthopaedic hospitals and clinics, chosen by Knee Replacement 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 Knee Replacement 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 orthopaedic hospitals and clinics, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three private orthopaedic hospitals and clinics, chosen by Knee Replacement 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.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 burden and does so: it discloses validation behavior in step 1, the exact return artifacts (summary, consent line, confirmation token), the outbound email with a mandatory click-through, and the fact that no provider sees the enquiry until that click. It also states the commercial context (providers may pay a fixed fee, never a share), which the agent must surface to the person.

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 scope negation and then cleanly sequenced as Step 1 / Step 2, which suits the two-call flow. Slightly penalized because the full consent paragraph is reproduced verbatim and already lives in the schema's consent description, making the block longer than strictly necessary.

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?

No output schema exists, so the description must describe return values — and it does, naming the summary, consent line and confirmation token from step 1 and the resulting email from step 2. For a nested-object, multi-step submission tool this is sufficient for an agent to act 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 100%, so the baseline is 3, but the description adds workflow meaning the schema cannot: answers are keyed by field key sourced from the enquiry_fields sibling, and confirmation is the token returned by step 1 and is only valid after the person approves the summary. That cross-tool and cross-step linkage goes beyond the per-field descriptions.

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?

Opens with a specific verb and resource ("Submits an enquiry to Knee Replacement Cost") and immediately bounds it with "NOT a purchase, NOT a guaranteed quote." The two-step framing and the reference to enquiry_fields make it distinguishable from the sibling describe/fields tools without opening any 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 call sequence: step 1 with answers + consent=true, show the person the summary and consent line, then step 2 only if the person agrees, adding the confirmation token. The gating condition for the second call ("only if the person agrees") is exactly the when/when-not guidance an agent needs.

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