FindWeedNY

Get one FindWeedNY review

get_review

Read-only

One review by slug (from search_reviews) with the full lab panel: every cannabinoid and terpene measured, batch number, price paid, COA link, and the excerpt. Full review text stays on the linked page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Review slug, e.g. "1slice-superboof-flower"

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`review`	No
`source`	No	Attribution line — CC BY 4.0, cite the row url
`message`	No
`dataUpdated`	No	ISO timestamp of the underlying directory export

Schema Changelog

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

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "dataUpdated": {
+      "description": "ISO timestamp of the underlying directory export",
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "review": {
+      "additionalProperties": true,
+      "properties": {
+        "batch": {
+          "type": "string"
+        },
+        "brand": {
+          "type": "string"
+        },
+        "brandSlug": {
+          "type": "string"
+        },
+        "brandUrl": {
+          "type": "string"
+        },
+        "cannabinoids": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "pct": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "name",
+              "pct"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "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"
+        },
+        "productUrl": {
+          "type": "string"
+        },
+        "rating": {
+          "description": "1–5, FindWeedNY's opinion",
+          "type": "number"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "strain": {
+          "type": "string"
+        },
+        "terpenes": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "pct": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "name",
+              "pct"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "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"
+    },
+    "source": {
+      "description": "Attribution line — CC BY 4.0, cite the row url",
+      "type": "string"
+    }
+  },
+  "required": [
+    "found"
+  ],
+  "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 already declare readOnlyHint=true, and the description adds meaningful behavioral context: the tool returns the full lab panel, batch number, price paid, COA link, and excerpt, while deliberately omitting the full review text. This sets accurate expectations about response content.

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 two sentences with no filler. It front-loads the core purpose, lists the return contents efficiently, and ends with a useful boundary about full review text.

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 simple single-parameter read-only tool with a provided output schema, the description is complete. It explains the input source, the returned fields, and an important limitation, leaving no major ambiguity for an agent.

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% and the schema already documents the slug parameter with an example. The description adds value by explaining that the slug originates from search_reviews, which clarifies how to obtain a valid value.

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 action and resource: retrieving a single review by slug. It also distinguishes itself from siblings like search_reviews by clarifying that the slug comes from search_reviews and by enumerating the unique full lab panel content returned.

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 clearly implies the correct workflow: first call search_reviews to obtain a slug, then call get_review with that slug. It does not explicitly list exclusions or alternative tools for other use cases, but the slug-source guidance is strong and unambiguous.

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?