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

Behavior4/5

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

Annotations provide readOnlyHint=true, so the agent knows this is a safe read operation. The description adds meaningful behavioral context beyond that: every review has a 1–5 rating, cannabis reviews include COA numbers and a certificate link, and rows carry an excerpt and url. It also discloses the default sort (date, newest first) and the limit cap (50) via the schema. It doesn't mention pagination behavior beyond the schema's offset description, but the schema already covers that.

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 a single dense paragraph that front-loads the core purpose, then details the review content, then filter/sort options, then example queries, then the row shape. Every sentence earns its place; no filler or repetition of the schema.

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 100% schema coverage, an output schema, and no required parameters, the description is complete. It explains what the tool returns, how to filter/sort, and gives example use cases. The only minor gap is not describing the exact output schema fields, but the output schema exists and the description mentions excerpt and url, so an agent has enough to call it correctly.

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 all 9 parameters. The description adds value by explaining the review content (COA numbers, terpenes, rating) and giving example queries, but it doesn't add much per-parameter meaning beyond what the schema provides. 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 states a specific verb ('search') and resource ('FindWeedNY product reviews'), and clearly distinguishes this tool from siblings like get_review (full review vs. rows with excerpt/url) and search_brands/search_dispensaries (product reviews vs. brands/dispensaries). It also enumerates the review content (rating, COA numbers, terpenes, link) and the filter/sort dimensions, so an agent can tell exactly what this tool returns.

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?

The description gives explicit example queries ('is brand X any good', 'best-tested flower', 'most terpene-rich vape') and states the filter/sort capabilities. It implies when to use this tool versus get_review (rows with excerpt and url vs. full review) and search_brands/search_dispensaries (product reviews vs. brand/dispensary search). This is strong routing guidance.

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?