FindWeedNY

Search FindWeedNY product reviews

search_reviews

Read-only

FindWeedNY's own independent, lab-anchored reviews of New York cannabis products (flower, vapes, concentrates, edibles). Every review has a 1–5 rating and, for cannabis products, the COA numbers: THC %, total terpenes %, top terpenes, plus a link to the certificate of analysis. Filter by brand, product type, strain, cultivation method, or minimum rating; sort by date, rating, or terpenes. Use this for "is brand X any good", "best-tested flower", or "most terpene-rich vape" questions. Rows carry an excerpt and a url to the full review.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Default date (newest first)
`brand`	No	Brand name or slug
`limit`	No	Max rows, default 10, cap 50
`query`	No	Text match on title, product, brand, or strain
`offset`	No	Rows to skip for paging: the result echoes `total` and `offset`, so request offset + limit for the next page
`strain`	No	Strain or type, e.g. "hybrid", "sativa", "indica", or a strain name
`min_rating`	No	1–5
`cultivation`	No	How the flower was grown, when the review records it
`product_type`	No	Kind of product reviewed

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`total`	Yes
`offset`	Yes
`source`	No	Attribution line — CC BY 4.0, cite the row url
`reviews`	Yes
`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 / cultivation / description

Added value: +"How the flower was grown, when the review records it"

addedInput schema / properties / product_type / description
```
Added value: +"Kind of product reviewed"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "dataUpdated": {
+      "description": "ISO timestamp of the underlying directory export",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "reviews": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "brand": {
+            "type": "string"
+          },
+          "brandSlug": {
+            "type": "string"
+          },
+          "brandUrl": {
+            "type": "string"
+          },
+          "coaUrl": {
+            "description": "Certificate of analysis",
+            "type": "string"
+          },
+          "cultivation": {
+            "type": "string"
+          },
+          "date": {
+            "type": "string"
+          },
+          "excerpt": {
+            "type": "string"
+          },
+          "price": {
+            "type": "string"
+          },
+          "product": {
+            "type": "string"
+          },
+          "productType": {
+            "description": "flower | vape | concentrate | edible | accessory | dispensary",
+            "type": "string"
+          },
+          "rating": {
+            "description": "1–5, FindWeedNY's opinion",
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "strain": {
+            "type": "string"
+          },
+          "thcPct": {
+            "description": "Total THC ≈ THCa×0.877 + Δ9, from the COA",
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topTerpenes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "totalTerpenesPct": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "rating",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "description": "Attribution line — CC BY 4.0, cite the row url",
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "reviews"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only say readOnlyHint=true; the description adds useful behavior beyond that: reviews are independent/lab-anchored, ratings are 1–5, cannabis reviews include COA numbers, and rows carry an excerpt and URL. There is no contradiction.

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 identity (independent lab-anchored reviews) and every sentence earns its place: content, filters/sorts, use cases, and row shape. It is compact for a 9-parameter search tool.

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 tool with 9 optional parameters, 100% schema coverage, an output schema, and a readOnlyHint annotation, the description is complete enough: it explains what is searched, what data is returned, and which queries it is meant for. Any remaining details (pagination, THC sort) are already in the schema.

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 parameters. The description summarizes filters and sorts but doesn't add meaning beyond the schema; it even omits sort=thc and the query/limit/offset parameters, all of which are covered by the schema. Baseline 3 is appropriate.

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 names a specific verb and resource—searching FindWeedNY's editorial cannabis reviews—and states the product categories, rating scale, and COA data, so an agent can separate it from search_brands/search_dispensaries. It also implies a list-style tool by mentioning rows with excerpts and URLs, distinguishing it from get_review.

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?

It gives concrete when-to-use examples ('is brand X any good', 'best-tested flower', 'most terpene-rich vape'). It does not explicitly name alternatives or say when not to use it, but the context is clear.

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?