Skip to main content
Glama

site

by uk.co.herniasurgerycost

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

submit_enquiry

Submits an enquiry to Hernia 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: "Happy for my details to go to private hospitals and surgical clinics, who'll price my repair directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to private hospitals and surgical clinics, who'll price my repair directly.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/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 executes superbly. It discloses the two-step confirmation requirement, validation behavior, the returned summary/token, the exact consent wording to show, and the post-submission email-link gating before any provider sees the enquiry. This is deep behavioral disclosure with zero reliance on structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place — the two-step protocol, consent wording, and email-link behavior are all essential for correct invocation. The 'NOT a purchase' disclaimer is front-loaded, and the step-1/step-2 numbering gives clear structure to a genuinely complex workflow.

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?

Despite having no output schema and no annotations, the description covers everything an agent needs: return values from step 1 are named, the consent requirement is quoted verbatim, the follow-up call condition is explicit, and post-submission behavior (email link, provider visibility) is disclosed. For a high-complexity two-step tool, nothing essential is missing.

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; the description adds workflow meaning beyond it by tying 'answers' to field keys from enquiry_fields and explaining when each parameter is used (step 1 needs answers+consent, step 2 adds confirmation). This contextual framing helps an agent know which parameters matter at which stage, which the schema alone does not convey.

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 Hernia Surgery Cost') and immediately scopes what it is NOT ('NOT a purchase, NOT a guaranteed quote'), separating it from any transactional sibling. The title reinforces this with 'two steps; not a purchase', making the tool's identity unmistakable.

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 provides an explicit two-step protocol: call with answers and consent=true to get a summary and token, then call again with the token only if the person agrees. It gives the exact condition for proceeding ('only if the person agrees') and references the sibling enquiry_fields as the source of answer keys, routing the agent correctly.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clear, separate role: enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry performs the submission. There is no meaningful overlap between the informational and action-oriented tools.

Naming Consistency4/5

Tool names are consistently lowercase snake_case and clearly reference the enquiry domain. Minor inconsistency exists because two names start with 'enquiry_' while one uses verb-first 'submit_enquiry', but the pattern is still predictable and readable.

Tool Count4/5

Three tools is a small but appropriate set for a narrow single-purpose workflow. Each tool earns its place by covering description, field discovery, and submission without unnecessary bloat.

Completeness4/5

The enquiry submission workflow is well covered: the agent can understand the process, retrieve all required fields, and complete the two-step consent confirm flow. A minor gap is the lack of any way to check enquiry status or cancel after submission, but this does not block the core purpose.

Resources