Findabis

Find cannabis strains

find_strains

Read-onlyIdempotent

Find cannabis strain profiles by name or genetics (Indica, Sativa or Hybrid). Returns up to 25 strains at a time (page on with offset) with page URL, slug, genetics and THC and CBD ranges. A strain is a plant lineage, not something a pharmacy dispenses — use find_products for that. Findabis publishes no effects, medical uses or side effects for strains, so none are returned and none should be inferred. For terpenes, flavours and lineage, use get_listing with kind "strain".

Input Schema

Name	Required	Description
`limit`	No	How many to return, 1-25. Default 10.
`query`	No	Strain name or nickname, e.g. "Gelato". Omit to browse.
`offset`	No	Skip this many results, for the next page (the answer says which offset comes next). Default 0.
`genetics`	No	The strain type: Indica, Sativa or Hybrid.

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

Changed6 schema fields changedOct 4, 2026

changedInput schema / properties / genetics / description

Previous value: -"Indica, Sativa or Hybrid."New value: +"The strain type: Indica, Sativa or Hybrid."

addedInput schema / properties / genetics / enum

Added value: +[
+  "Indica",
+  "Sativa",
+  "Hybrid"
+]

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: -"Strain name."New value: +"Strain name or nickname, e.g. \"Gelato\". Omit to browse."

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

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": {
+          "cbdPercent": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "genetics": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "thcPercent": {
+            "description": "A figure or a range, e.g. \"18-22\"",
+            "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",
+          "genetics",
+          "thcPercent",
+          "cbdPercent"
+        ],
+        "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.8/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the description goes further: it discloses page size (25), the offset paging mechanism, and — most valuably — that effects, medical uses and side effects are deliberately absent and must not be inferred. That negative disclosure directly prevents hallucinated output.

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 return shape, then disambiguation — good ordering with no filler. The enumeration of returned fields (page URL, slug, genetics, THC/CBD ranges) is slightly redundant given an output schema exists, but it is compact and aids selection.

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?

Covers everything an agent needs: what it searches, how paging works, what comes back, what deliberately does not come back, and which sibling to use for adjacent needs. With an output schema present, no further return-value detail is required.

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 meaning beyond it by explaining the offset as 'page on with `offset`' and tying limit to the 25-cap paging model. It does not restate query/genetics semantics, which the schema already handles well.

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 and resource ('Find cannabis strain profiles') plus the two lookup axes (name or genetics). It also preempts the most likely confusion by declaring a strain is a plant lineage, not a dispensable product, which separates it from find_products without the agent needing to open either schema.

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?

Explicit routing to alternatives: find_products for dispensable products, get_listing with kind "strain" for terpenes/flavours/lineage. It also gives a positive usage cue ('Omit query to browse' is in schema, and the description frames name/genetics as the two search modes).

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.