Skip to main content
Glama

Compare clinics or pharmacies

compare_providers
Read-onlyIdempotent

Compare 2-6 clinics (fees, year-one cost, CQC, ratings) or 2-6 pharmacies (delivery, GPhC, ratings) side by side. Services only, never medicines. Example: {"kind":"clinic","slugs":["clinic-a","clinic-b"]}

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": {
      "kind": "<kind>",
      "slugs": "<slugs>"
    },
    "name": "compare_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat the slugs are.
slugsYes2-6 slugs.
patientTypeNoClinics: year-one pricing route. Default NEW_PATIENT.
followUpsPerYearNoClinics: follow-ups a year. Default 4.
prescriptionsPerYearNoClinics: prescriptions a year. Default 12.

Output Schema

NameRequiredDescriptionDefault
kindYes
noteYes
clinicsNo
missingYesSlugs with no such listing
pharmaciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / clinics / items / properties / partnerPharmacies / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / clinics / items / properties / partnerPharmacies / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / pharmacies / items / properties / partnerClinics / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / pharmacies / items / properties / partnerClinics / minimum
      Added value: +-9007199254740991
  2. Changed6 schema fields changed
    • changedInput schema / properties / followUpsPerYear / description
      Previous value: -"Clinics: follow-up consultations a year. Default 4."New value: +"Clinics: follow-ups a year. Default 4."
    • changedInput schema / properties / kind / description
      Previous value: -"Compare clinics or pharmacies (not both at once)."New value: +"What the slugs are."
    • changedInput schema / properties / patientType / description
      Previous value: -"Clinics: price year one as NEW_PATIENT (default), TRANSFER or ACTIVE_PATIENT."New value: +"Clinics: year-one pricing route. Default NEW_PATIENT."
    • changedInput schema / properties / prescriptionsPerYear / description
      Previous value: -"Clinics: repeat prescriptions a year. Default 12."New value: +"Clinics: prescriptions a year. Default 12."
    • changedInput schema / properties / slugs / description
      Previous value: -"2-6 page slugs from find_clinics / find_pharmacies."New value: +"2-6 slugs."
    • changedInput schema / properties / slugs / items / description
      Previous value: -"The page slug from a find_* tool or search_directory, e.g. \"green-leaf-clinic\"."New value: +"Page slug."
  3. Changed1 schema field changed
    • changedInput schema / properties / slugs / items / description
      Previous value: -"The page slug from a find_* tool or search_findabis, e.g. \"green-leaf-clinic\"."New value: +"The page slug from a find_* tool or search_directory, e.g. \"green-leaf-clinic\"."
  4. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior detail by naming what is compared (fees, year-one cost, CQC, ratings / delivery, GPhC, ratings) and excluding medicines. It says nothing, however, about result ordering, missing/invalid slug handling, or limits beyond the 2-6 cap, which the schema already encodes.

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?

Three short sentences: capability and multiplicity first, scope exclusion second, minimal invocation example last. No filler, and the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need no explanation, and the schema plus annotations carry parameter bounds and the safety profile. For a read-only, five-parameter comparison tool the description covers kind, count, compared attributes, and scope, leaving nothing an agent needs in order to call it 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 schema already documents all five parameters including defaults and bounds; baseline would be 3. The embedded example adds a bit of value by demonstrating the kind+slugs pairing, and 'year-one cost' signals that patientType drives the pricing route, though followUpsPerYear and prescriptionsPerYear are left entirely to the schema.

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?

States a specific verb (Compare) plus two resource types (clinics, pharmacies) with the exact fields compared, and the 'side by side' framing plus the 2-6 multiplicity separates it from single-entity siblings like get_clinic or find_clinics. The 'Services only, never medicines' line further bounds the resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes clear this is the multi-provider comparison path and gives a concrete invocation example, so an agent knows when to reach for it over a single-provider lookup. It stops short of naming an alternative tool or stating an explicit when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.