FindWeedNY

Get dispensary details

get_dispensary

Read-only

Full public record for one dispensary by OCM license number (e.g. "OCM-CAURD-23-000023"), verified alias, or legacy id. Includes hours, description, and license dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	License number, alias, or legacy id

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`source`	No	Attribution line — CC BY 4.0, cite the row url
`message`	No
`dispensary`	No
`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"

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"
+    },
+    "dispensary": {
+      "additionalProperties": true,
+      "properties": {
+        "address": {
+          "type": "string"
+        },
+        "amenities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "city": {
+          "type": "string"
+        },
+        "claimed": {
+          "type": "boolean"
+        },
+        "closure": {
+          "additionalProperties": true,
+          "description": "Present only when the shop has closed",
+          "properties": {
+            "announcedDate": {
+              "type": "string"
+            },
+            "date": {
+              "type": "string"
+            },
+            "notes": {
+              "type": "string"
+            },
+            "reason": {
+              "type": "string"
+            },
+            "temporary": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "county": {
+          "type": "string"
+        },
+        "dba": {
+          "description": "Legal entity name",
+          "type": "string"
+        },
+        "deliveryZipCodes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "description": {
+          "type": "string"
+        },
+        "distance": {
+          "description": "Miles from `near`, when a near point was given",
+          "type": "number"
+        },
+        "geocodeAccuracy": {
+          "type": "string"
+        },
+        "googleRating": {
+          "type": "number"
+        },
+        "googleReviewCount": {
+          "type": "number"
+        },
+        "hours": {
+          "additionalProperties": true,
+          "description": "Posted hours by weekday",
+          "properties": {},
+          "type": "object"
+        },
+        "hoursToday": {
+          "type": "string"
+        },
+        "id": {
+          "description": "OCM license number (directory id)",
+          "type": "string"
+        },
+        "isDeliveryOnly": {
+          "type": "boolean"
+        },
+        "isMedical": {
+          "type": "boolean"
+        },
+        "isMicrobusiness": {
+          "type": "boolean"
+        },
+        "lastVerified": {
+          "type": "string"
+        },
+        "latitude": {
+          "type": "number"
+        },
+        "licenseExpirationDate": {
+          "type": "string"
+        },
+        "licenseIssueDate": {
+          "type": "string"
+        },
+        "licenseType": {
+          "type": "string"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "name": {
+          "type": "string"
+        },
+        "neighborhood": {
+          "description": "NYC neighborhood, when applicable",
+          "type": "string"
+        },
+        "offersDelivery": {
+          "type": "boolean"
+        },
+        "openNow": {
+          "description": "Open right now by posted hours (New York time); absent when hours are unknown",
+          "type": "boolean"
+        },
+        "operationalStatus": {
+          "description": "Active | Non-Operational | Unknown",
+          "type": "string"
+        },
+        "phone": {
+          "type": "string"
+        },
+        "retailDateOpened": {
+          "description": "YYYY-MM-DD the shop opened to the public",
+          "type": "string"
+        },
+        "state": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        },
+        "tier": {
+          "description": "open | coming-soon | delivery-only",
+          "type": "string"
+        },
+        "url": {
+          "description": "findweedny.com page — cite this",
+          "type": "string"
+        },
+        "website": {
+          "type": "string"
+        },
+        "zipCode": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "url"
+      ],
+      "type": "object"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution line — CC BY 4.0, cite the row url",
+      "type": "string"
+    }
+  },
+  "required": [
+    "found"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The readOnlyHint annotation already conveys that this is a safe read operation, and the description adds concrete behavioral detail by listing the record contents (hours, description, license dates). It does not disclose error handling or edge cases, but for a simple lookup tool with the safety profile already annotated, this is adequate.

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 the primary purpose front-loaded and the specifics (identifier types and included data) following. Every phrase adds information; there is no fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter get operation with an output schema and a readOnly annotation, the description covers the essential aspects: what identifiers are accepted and what fields are returned. It does not mention potential failure modes or authentication, but these are less critical given the simple interface and the presence of the output schema.

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?

The input schema already describes the id parameter as 'License number, alias, or legacy id', achieving 100% coverage. The description reinforces this and adds a concrete example of the license format ('OCM-CAURD-23-000023'), which clarifies the expected input beyond the generic schema text. This additional example provides meaningful 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 clearly states the tool fetches the full public record for a single dispensary, identifies the accepted identifier types (OCM license number with an example, verified alias, or legacy id), and enumerates included fields (hours, description, license dates). This distinguishes it from sibling search tools like search_dispensaries, which return lists, and other get_* tools that target different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool—when you have a specific identifier for a dispensary and want its full record—but it does not explicitly contrast it with alternatives or state when not to use it. An agent could infer the distinction from the singular 'one dispensary' versus the sibling search_dispensaries, but no direct guidance is given.

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?