FindWeedNY

Get Metrc NY market landscape

get_metrc_market_landscape

Read-only

Statewide New York cannabis market aggregates, crawled from Metrc’s public Cannabis Market Landscape dashboard — the seed-to-sale system every licensee reports into. Use it for market-size and trend questions (how much does NY sell a month, which regions and product categories, how many licenses exist and how fast are they being issued, what share of lab tests pass). Returns a summary of the four headline numbers plus a metrics array: monthly retail sales, cumulative sales, units sold, transaction count, basket size, average price per unit, lab test volume and pass rate, retail sales by region and by product category, active licenses by type and by region, monthly new licenses and cumulative license growth. Narrow it with section or metric; metricsAvailable always lists everything in the snapshot. This is dashboard-level aggregate data, not transaction-level Metrc records, and license counts may differ from NY OCM totals. For dispensary-by-dispensary counts use get_market_stats instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`metric`	No	Only these metric names (see metricsAvailable), e.g. ["retail_sales_by_region"].
`section`	No	Only metrics from this dashboard tab.

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`source`	No	Attribution line — CC BY 4.0, cite the row url
`message`	No
`dataUpdated`	No	ISO timestamp of the feed this result came from: dispensary directory (OCM refresh), deals export, brand-availability export, or review index
`marketLandscape`	No	Aggregate values crawled from Metrc’s public New York Cannabis Market Landscape dashboard

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 13, 2026

addedInput schema / additionalProperties
```
Added value: +true
```

addedInput schema / properties / metric

Added value: +{
+  "description": "Only these metric names (see metricsAvailable), e.g. [\"retail_sales_by_region\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / section

Added value: +{
+  "description": "Only metrics from this dashboard tab.",
+  "enum": [
+    "market_overview",
+    "license_activity"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / marketLandscape / properties / licenseActivity

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "activeLicenses": {
-      "type": "number"
-    },
-    "cumulativeLicenseGrowth": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "period": {
-            "type": "string"
-          },
-          "value": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "period",
-          "value"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "monthlyNewLicenses": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "period": {
-            "type": "string"
-          },
-          "value": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "period",
-          "value"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "newLicensesYearToDate": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / marketLandscape / properties / marketOverview

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "activeLicenses": {
-      "type": "number"
-    },
-    "licenseTypeDistribution": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "count": {
-            "type": "number"
-          },
-          "licenseType": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "licenseType",
-          "count"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "monthlyRetailSales": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "period": {
-            "type": "string"
-          },
-          "value": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "period",
-          "value"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "overallAverageTestPassRate": {
-      "type": "number"
-    },
-    "totalRetailSales": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / marketLandscape / properties / meta / properties / dateRange / description
```
Added value: +"The dashboard filter this snapshot was read under; YTD is the default."
```
addedOutput schema / properties / marketLandscape / properties / meta / properties / fetchedAt / description
```
Added value: +"When this snapshot was taken. The dashboard itself keeps no archive."
```

addedOutput schema / properties / marketLandscape / properties / metrics

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "derivedFrom": {
+        "description": "Present only when FindWeedNY computed this metric by dividing the listed series, because the dashboard did not return its own element that day.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "dimension": {
+        "description": "What each point’s category is: region | product_category | license_type. Absent on scalars and monthly series.",
+        "type": "string"
+      },
+      "metric": {
+        "type": "string"
+      },
+      "points": {
+        "items": {
+          "additionalProperties": true,
+          "properties": {
+            "category": {
+              "description": "The breakdown member. Present on breakdowns only — see dimension.",
+              "type": "string"
+            },
+            "period": {
+              "description": "ISO month start (YYYY-MM-01). Present on monthly series only.",
+              "type": "string"
+            },
+            "value": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "section": {
+        "description": "market_overview | license_activity — which dashboard tab published it",
+        "type": "string"
+      },
+      "title": {
+        "description": "The chart title as it appears on the dashboard",
+        "type": "string"
+      },
+      "unit": {
+        "description": "USD | licenses | units | transactions | tests | percent | USD per unit | USD per transaction",
+        "type": "string"
+      }
+    },
+    "required": [
+      "section",
+      "metric",
+      "title",
+      "unit",
+      "points"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / marketLandscape / properties / metricsAvailable

Added value: +{
+  "description": "Every metric in the snapshot, including any filtered out of this response. Call again with `metric` to fetch one.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / marketLandscape / properties / summary

Added value: +{
+  "additionalProperties": true,
+  "description": "The four headline numbers, so simple questions do not need the metrics array.",
+  "properties": {
+    "activeLicenses": {
+      "type": "number"
+    },
+    "newLicensesYearToDate": {
+      "type": "number"
+    },
+    "overallAverageTestPassRate": {
+      "description": "Percent, 0-100.",
+      "type": "number"
+    },
+    "totalRetailSales": {
+      "description": "Year-to-date retail sales in USD, at full precision.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

AddedSep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation it discloses the data's provenance (Metrc dashboard crawl), its granularity (dashboard-level aggregates, not transaction records), and a real caveat that license counts may differ from NY OCM totals. These are behavioral traits the annotations cannot convey.

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?

Dense but front-loaded: purpose first, then use cases, then a detailed inventory of returned metrics, then caveats and the sibling pointer. The metric enumeration is long but earns its place by telling the agent what questions the tool can answer.

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?

Even though an output schema exists, the description covers the return shape (summary + metrics array), the filter semantics, and the data caveats, leaving no gap for correct invocation.

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%, so the baseline is 3, but the description adds genuine value: it explains that section/metric narrow the result set and that metricsAvailable always enumerates everything in the snapshot, telling the agent how the filters interact with the payload.

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?

States a specific verb+resource (statewide NY cannabis market aggregates from Metrc's public dashboard) and squarely distinguishes itself from get_market_stats for dispensary-level data. An agent can pick this over siblings without opening a schema.

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?

Explicitly names when to use it (market-size and trend questions, with concrete examples like monthly sales, regions, license issuance, lab pass rates) and when not to (transaction-level Metrc records; dispensary-by-dispensary counts, routed to get_market_stats).

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?