Skip to main content
Glama

Find dispensing pharmacies

find_pharmacies
Read-onlyIdempotent

Find UK pharmacies that dispense a clinic's prescription, nearest first with near, filtered by delivery, collection or rating. Never stock or medicine prices. Example: {"near":"M1 1AE","delivers":true}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_pharmacies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoUK postcode or town; nearest first.
pageNo60-row window; the answer says when there is another.
sortNoDefault distance with `near`, else az.
limitNoDefault 10.
queryNoPharmacy name.
offsetNoRows to skip.
deliversNoDelivers only.
minRatingNoMinimum review average.
collectionNoCollection only.
radiusMilesNoMiles from `near`.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageNoWhich window of 60 directory rows this answer read
totalYesHow many matched in all; narrow the query when this exceeds the results
resultsYes
directoryTotalNoThe whole directory, when the tool read one window of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / directoryTotal / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / directoryTotal / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / page / minimum
      Added value: +-9007199254740991
    • changedOutput schema / properties / results / items / properties / rating / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "average": {
      -        "type": "number"
      -      },
      -      "count": {
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "average",
      -      "count"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "average": {
      +        "type": "number"
      +      },
      +      "count": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "average",
      +      "count"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / total / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total / minimum
      Added value: +-9007199254740991
  2. Changed10 schema fields changed
    • changedInput schema / properties / collection / description
      Previous value: -"Only pharmacies offering in-person collection."New value: +"Collection only."
    • changedInput schema / properties / delivers / description
      Previous value: -"Only pharmacies that deliver (most dispense UK-wide by post)."New value: +"Delivers only."
    • changedInput schema / properties / limit / description
      Previous value: -"How many to return, 1-25. Default 10."New value: +"Default 10."
    • changedInput schema / properties / minRating / description
      Previous value: -"Only pharmacies with patient reviews averaging 3+ or 4+."New value: +"Minimum review average."
    • changedInput schema / properties / near / description
      Previous value: -"A UK postcode, outcode or town, e.g. \"M1 1AE\", \"LS6\" or \"Bristol\". Sorts nearest first and adds miles."New value: +"UK postcode or town; nearest first."
    • changedInput schema / properties / offset / description
      Previous value: -"Skip this many results, for the next page (the answer says which offset comes next). Default 0."New value: +"Rows to skip."
    • changedInput schema / properties / page / description
      Previous value: -"Which window of 60 directory rows to read; `offset` pages inside it. Default 1. The answer says when a later window exists."New value: +"60-row window; the answer says when there is another."
    • changedInput schema / properties / query / description
      Previous value: -"Pharmacy name, matched as text. For a place use `near`."New value: +"Pharmacy name."
    • changedInput schema / properties / radiusMiles / description
      Previous value: -"Only within this many miles of `near`. Ignored without `near`."New value: +"Miles from `near`."
    • changedInput schema / properties / sort / description
      Previous value: -"distance (default with `near`), az (default otherwise), za, city, rating."New value: +"Default distance with `near`, else az."
  3. Changed3 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which window of 60 directory rows to read; `offset` pages inside it. Default 1. The answer says when a later window exists.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / directoryTotal
      Added value: +{
      +  "description": "The whole directory, when the tool read one window of it",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "Which window of 60 directory rows this answer read",
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Skip this many results, for the next page (the answer says which offset comes next). Default 0.",
      +  "maximum": 500,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  5. Changed10 schema fields changed
    • addedInput schema / properties / collection
      Added value: +{
      +  "description": "Only pharmacies offering in-person collection.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / delivers / description
      Previous value: -"Only pharmacies that offer delivery."New value: +"Only pharmacies that deliver (most dispense UK-wide by post)."
    • addedInput schema / properties / minRating
      Added value: +{
      +  "description": "Only pharmacies with patient reviews averaging 3+ or 4+.",
      +  "enum": [
      +    "3_plus",
      +    "4_plus"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / near
      Added value: +{
      +  "description": "A UK postcode, outcode or town, e.g. \"M1 1AE\", \"LS6\" or \"Bristol\". Sorts nearest first and adds miles.",
      +  "maxLength": 64,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Pharmacy name, town or postcode, matched as text (not by distance). Omit to list all."New value: +"Pharmacy name, matched as text. For a place use `near`."
    • addedInput schema / properties / radiusMiles
      Added value: +{
      +  "description": "Only within this many miles of `near`. Ignored without `near`.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 500,
      +  "type": "number"
      +}
    • changedInput schema / properties / sort / description
      Previous value: -"az (default), za, or by town."New value: +"distance (default with `near`), az (default otherwise), za, city, rating."
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "az",
      -  "za",
      -  "city"
      -]New value: +[
      +  "distance",
      +  "az",
      +  "za",
      +  "city",
      +  "rating"
      +]
    • addedOutput schema / properties / results / items / properties / distanceMiles
      Added value: +{
      +  "description": "Miles from `near`; null when no place was given",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "name",
      -  "slug",
      -  "url",
      -  "city",
      -  "postcode",
      -  "offersDelivery",
      -  "offersCollection",
      -  "rating"
      -]New value: +[
      +  "name",
      +  "slug",
      +  "url",
      +  "city",
      +  "postcode",
      +  "distanceMiles",
      +  "offersDelivery",
      +  "offersCollection",
      +  "rating"
      +]
  6. Changed6 schema fields changed
    • changedInput schema / properties / delivers / description
      Previous value: -"Only pharmacies that deliver."New value: +"Only pharmacies that offer delivery."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 10."New value: +"How many to return, 1-25. Default 10."
    • changedInput schema / properties / query / description
      Previous value: -"Name, city or postcode."New value: +"Pharmacy name, town or postcode, matched as text (not by distance). Omit to list all."
    • addedInput schema / properties / query / maxLength
      Added value: +120
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "az (default), za, or by town.",
      +  "enum": [
      +    "az",
      +    "za",
      +    "city"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "note": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "city": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "offersCollection": {
      +            "type": "boolean"
      +          },
      +          "offersDelivery": {
      +            "type": "boolean"
      +          },
      +          "postcode": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "rating": {
      +            "anyOf": [
      +              {
      +                "additionalProperties": false,
      +                "properties": {
      +                  "average": {
      +                    "type": "number"
      +                  },
      +                  "count": {
      +                    "type": "integer"
      +                  }
      +                },
      +                "required": [
      +                  "average",
      +                  "count"
      +                ],
      +                "type": "object"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Published patient reviews; null when there are none"
      +          },
      +          "slug": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "anyOf": [
      +              {
      +                "format": "uri",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Canonical Findabis page, absolute; null when the listing has no page"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "slug",
      +          "url",
      +          "city",
      +          "postcode",
      +          "offersDelivery",
      +          "offersCollection",
      +          "rating"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "How many matched in all; narrow the query when this exceeds the results",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "total"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety and closed-dataset profile is covered. Beyond that, the description adds a genuine content boundary ('Never stock or medicine prices') that the annotations cannot express, which prevents an agent from misusing results as pricing data. It stops short of noting auth requirements or result volume limits beyond what the page/limit schema fields already state.

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 tight sentences: what it does, what it never returns, then a usable example. The ordering behavior and the exclusion both land before any detail, with no filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-shape explanation is unnecessary, and the 10 optional parameters are individually documented in the schema. The description covers purpose, ordering default when `near` is supplied, filter families, and the price/stock exclusion. Minor gap: it doesn't mention that the tool is location-dependent or what happens when `near` is omitted, though the schema's sort default hints at it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the 10 parameters is already documented, including defaults for sort, limit and page. The description's only additions are the combined-filter phrasing ('delivery, collection or rating') and a concrete example call, which shows `near` and `delivers` composed but adds no syntax or precedence detail beyond the schema. Baseline 3 is appropriate.

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 (find), a specific resource (UK dispensing pharmacies for a clinic's prescription), and a scope constraint ('Never stock or medicine prices') that separates it from product/stock lookup siblings. The nearest-first ordering behavior is also named, so an agent can tell this apart from find_products or get_pharmacy without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description conveys that this is a filtered pharmacy lookup with proximity, delivery, collection and rating refinements, and explicitly excludes stock/price questions. It names no alternative for the excluded cases (e.g., which tool to use for medicine prices or how to get one pharmacy's details) and gives no prerequisites, leaving the agent to infer routing from sibling names alone.

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.