Findabis

Find dispensing pharmacies

find_pharmacies

Read-onlyIdempotent

Find UK pharmacies that dispense cannabis-based medicines against a prescription a clinic has already issued. Use near (postcode or town) for nearest first with miles; filter by delivery, in-person collection and review score. Returns up to 25 pharmacies at a time (page on with offset) with slug, page URL, town, distance, delivery and collection, and review score. A pharmacy cannot prescribe. It does not return stock, prices, or which products a pharmacy holds: those are shown only to patients and professionals with access. For delivery prices and GPhC registration use get_listing, or compare_providers for several.

Input Schema

Name	Required	Description
`near`	No	A UK postcode, outcode or town, e.g. "M1 1AE", "LS6" or "Bristol". Sorts nearest first and adds miles.
`sort`	No	distance (default with `near`), az (default otherwise), za, city, rating.
`limit`	No	How many to return, 1-25. Default 10.
`query`	No	Pharmacy name, matched as text. For a place use `near`.
`offset`	No	Skip this many results, for the next page (the answer says which offset comes next). Default 0.
`delivers`	No	Only pharmacies that deliver (most dispense UK-wide by post).
`minRating`	No	Only pharmacies with patient reviews averaging 3+ or 4+.
`collection`	No	Only pharmacies offering in-person collection.
`radiusMiles`	No	Only within this many miles of `near`. Ignored without `near`.

Output Schema

Name	Required	Description
`note`	No
`total`	Yes	How many matched in all; narrow the query when this exceeds the results
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

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"
+}

Changed10 schema fields changedOct 9, 2026

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"
+]

Changed6 schema fields changedOct 4, 2026

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"
+}

First observedSep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral limits: it returns up to 25 results at a time, paginates via offset, excludes stock/prices/product holdings, and notes that those restricted fields are shown only to patients and professionals with access.

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 front-loaded with the core purpose, then covers usage, return shape, limitations, and alternatives in dense, useful sentences. There is no redundant or filler text.

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?

Given the annotations and output schema, the description is complete enough for an agent to call the tool correctly. It covers purpose, filtering, pagination, return fields, access limitations, and when to use sibling tools instead.

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 the parameters are already documented in the schema. The description reinforces key usage such as `near` triggering nearest-first miles and filters, but it does not add syntax or semantics beyond what the schema already provides.

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: finding UK pharmacies that dispense cannabis-based medicines against an already-issued clinic prescription. It also distinguishes the tool from get_listing and compare_providers, and explicitly notes that a pharmacy cannot prescribe.

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 explains how to use `near` for nearest-first distance results, how to filter by delivery, collection, and review score, and how to page with `offset`. It also names alternatives: get_listing for delivery prices and GPhC registration, and compare_providers for comparing several providers.

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

All Findabis tools Inspect

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.