FindWeedNY

Search NY cannabis brands

search_brands

Read-only

Search cannabis brands sold in New York. Filter by name, product category (e.g. flower, vapes, edibles, pre-rolls), brand type (local / national / mso), New York origin, microbusiness licensees, grow method (indoor / outdoor / mixed-light / combination — from OCM cultivator licenses; "sun-grown" and "greenhouse" accepted as aliases), ownership certification (woman-owned, veteran-owned, bipoc-owned, social-equity…), tag, or parent brand (the house that owns it — e.g. which brands PharmaCann or 1 Off run in NY). Rows include growType, licenseType, certifications, tags and how many dispensaries stock the brand.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Catalog tag, e.g. "craft", "small-batch", "living-soil", "hudson-valley"
`type`	No	Brand type: local (NY), national, or multi-state operator
`limit`	No	Max rows, default 10, cap 50
`query`	No	Substring match on brand name
`offset`	No	Rows to skip for paging: the result echoes `total` and `offset`, so request offset + limit for the next page
`parent`	No	Only brands owned by this parent brand / house (slug or name), e.g. "1-off", "PharmaCann", "GTI"
`category`	No	Product category, e.g. "vapes"
`ny_based`	No	Only brands headquartered / grown in New York
`grow_type`	No	Cultivation method from OCM license data. sun-grown = outdoor; greenhouse = mixed-light or combination
`certification`	No	Ownership/impact certification, e.g. "woman-owned", "veteran-owned", "bipoc-owned", "social-equity"
`microbusiness`	No	Only brands holding a NY microbusiness license

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes
`brands`	Yes
`offset`	Yes
`source`	No	Attribution line — CC BY 4.0, cite the row url
`dataUpdated`	No	ISO timestamp of the feed this result came from: dispensary directory (OCM refresh), deals export, brand-availability export, or review index

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / properties / dataUpdated / description

Previous value: -"ISO timestamp of the underlying directory export"New value: +"ISO timestamp of the feed this result came from: dispensary directory (OCM refresh), deals export, brand-availability export, or review index"

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / ny_based / description

Added value: +"Only brands headquartered / grown in New York"

addedInput schema / properties / type / description

Added value: +"Brand type: local (NY), national, or multi-state operator"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "brands": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "certifications": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "dispensaryCount": {
+            "description": "Stores currently stocking the brand",
+            "type": "number"
+          },
+          "founded": {
+            "type": "number"
+          },
+          "growType": {
+            "description": "indoor | outdoor | mixed-light | combination (from OCM cultivator licenses)",
+            "type": "string"
+          },
+          "headquarters": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "isMSO": {
+            "type": "boolean"
+          },
+          "isMicrobusiness": {
+            "type": "boolean"
+          },
+          "isNewYorkBased": {
+            "type": "boolean"
+          },
+          "licenseNumber": {
+            "type": "string"
+          },
+          "licenseType": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "parentBrand": {
+            "description": "Slug of the house brand that owns this one",
+            "type": "string"
+          },
+          "productCategories": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "shortDescription": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "type": {
+            "description": "local | national | mso",
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "slug",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "dataUpdated": {
+      "description": "ISO timestamp of the underlying directory export",
+      "type": "string"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "source": {
+      "description": "Attribution line — CC BY 4.0, cite the row url",
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "brands"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavior beyond that: it explains the grow-method aliases and their source in OCM cultivator licenses, and states exactly what fields rows contain, including 'how many dispensaries stock the brand.' This gives the agent concrete expectations of the tool's output behavior.

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 purpose is front-loaded, and all filter options are grouped into a single well-structured sentence with a second sentence covering output fields. Despite the breadth of 11 parameters, there is no fluff, repetition, or filler—every clause adds filtering or result context.

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 read-only search tool with 11 optional parameters and an output schema, the description covers the full filter surface, the data source, alias resolution, and row contents. An agent has everything needed to decide whether this tool fits the user's query.

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 schema already documents every parameter. The description largely restates those semantics with examples rather than adding entirely new meaning, though it does helpfully compress the grow_type aliases and brand-type categories into one readable overview.

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 opens with a specific verb and resource: 'Search cannabis brands sold in New York.' It then enumerates the main filter dimensions, distinguishing this broad search operation from sibling tools like get_brand without needing to name them explicitly.

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?

The description makes the search context clear by listing the many filter axes, implying this is the go-to tool for multi-dimensional brand discovery. It does not explicitly name alternatives or when-not-to-use it, but the broad-scoped phrasing provides unambiguous context.

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

All FindWeedNY tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?