findabis

Find medical cannabis products

find_products

Read-onlyIdempotent

Find cannabis-based medicines on the UK market by product, brand or strain name, or by dose form. Returns up to 25 products with page URL, slug, brand, dose form, THC and CBD content, and the latest price a UK pharmacy charged (naming no pharmacy) when Findabis publishes one. It does not return stock, pack sizes on offer, per-pharmacy prices or which pharmacies dispense a product: those are shown only to patients and professionals with access. A listing is not a statement that a product suits anyone. For one product in full, use get_product with its slug.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Alphabetical, name_asc (default) or name_desc.
`limit`	No	How many to return, 1-25. Default 10.
`query`	No	Product, brand or strain name, e.g. "Pink Kush" or "Tilray". Omit to browse.
`category`	No	Dose form. CARTRIDGE is a vape cartridge.

Output Schema

TableJSON 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.

Changed7 schema fields changedOct 4, 2026

changedInput schema / properties / category / description

Previous value: -"Dose form."New value: +"Dose form. CARTRIDGE is a vape cartridge."

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: -"Product, brand or strain name."New value: +"Product, brand or strain name, e.g. \"Pink Kush\" or \"Tilray\". Omit to browse."

addedInput schema / properties / query / maxLength
```
Added value: +120
```

changedInput schema / properties / sort / description

Previous value: -"Default name_asc."New value: +"Alphabetical, name_asc (default) or name_desc."

changedInput schema / properties / sort / enum

Previous value: -[
-  "name_asc",
-  "price_asc",
-  "price_desc"
-]New value: +[
+  "name_asc",
+  "name_desc"
+]

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": {
+          "brand": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "Dose form: FLOWER, OIL, CAPSULE, EDIBLE, TOPICAL, CARTRIDGE or HASH",
+            "type": "string"
+          },
+          "cbd": {
+            "description": "CBD content as the page prints it, unit included",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "discontinued": {
+            "type": "boolean"
+          },
+          "latestPrice": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "amount": {
+                    "type": "number"
+                  },
+                  "currency": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "amount",
+                  "currency"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The latest price any UK pharmacy charged, naming no pharmacy; null when not published"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "thc": {
+            "description": "THC content as the page prints it, unit included",
+            "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",
+          "brand",
+          "category",
+          "thc",
+          "cbd",
+          "discontinued",
+          "latestPrice"
+        ],
+        "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.6/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantive context beyond them: it names what IS returned (URL, slug, brand, dose form, THC/CBD, latest pharmacy price) and, crucially, what is NOT (stock, pack sizes, per-pharmacy prices, dispensing pharmacies), explaining that the latter is access-restricted. The 'not a statement that a product suits anyone' caveat is an extra, non-obvious behavioral disclosure.

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 purpose, then output scope, exclusions, disclaimer, and the sibling routing – each sentence is informative. It is slightly dense/run-on and the return-field enumeration is partly redundant given an output schema exists, but nothing is filler.

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?

For a 4-param, zero-required search tool with an output schema, the description supplies everything an agent needs: search axes, result cap, what is and isn't returned, the access-restriction rationale, and routing to get_product. No meaningful gap remains.

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 coverage is 100%, so the schema already documents all four parameters including enum values and the 1-25 limit. The description only restates the query axes ('by product, brand or strain name, or by dose form') without adding syntax or semantics beyond what the schema provides, so baseline 3 applies.

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') and resource ('cannabis-based medicines on the UK market') and enumerates the search axes: product, brand, strain name, or dose form. It clearly distinguishes itself from the sibling get_product by scope (search vs. one product in full).

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?

Explicitly names the alternative and the condition that selects it: 'For one product in full, use get_product with its slug.' It also implicitly frames this tool as the browse/search entry point when the user has only a name or dose form.

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.

Resources

Need Help?