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 underlying directory export

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds valuable behavioral context beyond annotations by specifying the row fields returned (growType, licenseType, certifications, tags, dispensary count) and explaining grow-type aliases such as 'sun-grown' and 'greenhouse'. This helps the agent set expectations for output without contradicting the read-only annotation.

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?

The description is a single dense sentence that front-loads the core action and then enumerates filters efficiently. It is not overly verbose given 11 parameters, though a bulleted structure could improve scanability. Every clause contributes useful information or examples.

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 11-parameter search tool with an output schema, the description covers all filter dimensions, provides domain-specific nuance (grow method aliases, parent brand concept), and describes the shape of returned rows. Pagination and limits are already covered by the input schema, so nothing critical is missing for an agent to call this tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by giving concrete examples for category, certification, and parent brand (e.g., 'PharmaCann or 1 Off'), and by clarifying that grow_type aliases map to OCM cultivator license data. These examples and mappings help an agent choose parameter values more accurately.

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 clear verb-resource pairing ('Search cannabis brands sold in New York') and immediately enumerates the filter dimensions, making the tool's purpose unmistakable. The reference to 'Rows include...' and the search semantics distinguishes it from the singular get_brand sibling, and the resource 'brands' differentiates it from search_dispensaries and search_reviews.

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 provides clear context on when to use the tool: any search for cannabis brands with optional filters across many attributes. It does not explicitly name alternatives like get_brand for single-brand lookups, so it stops short of a 5, but the usage context is strong and no exclusions are needed given the sibling set.

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?