Skip to main content
Glama

Get breweries, wineries, cideries and distilleries

get_beverage_places
Read-only

Search manufacturer listings compiled from the New York State Liquor Authority public active-license dataset (data.ny.gov 9s3h-dpkz) for counties from Broome west through Erie and Niagara, including the Finger Lakes and Southern Tier. Hours, websites, taps and food are included only when a separate public source or a claimed listing has them. Independent compilation, not a government site.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_beverage_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName or address text
latNoLatitude for near-me filtering
lonNoLongitude for near-me filtering
townNo
typeNobrewery, winery, cidery, distillery, or meadery
countyNo
radiusNoRadius in miles (default 25)
open_nowNoIf true, only places with verified hours that are open at this moment in America/New_York. Places with unknown hours are omitted, never treated as open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description's job is added context, and it delivers: it discloses that hours, websites, taps and food are populated only when a separate public source or claimed listing supplies them, which sets correct expectations about sparse fields. The 'independent compilation, not a government site' note clarifies accuracy and authority of the data. It stops short of describing result ordering, pagination, or what happens with zero matches.

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?

Two sentences, both doing work, with the geographic scope front-loaded. The dataset identifier and provenance note consume space that could have been spent on usage guidance, but they carry legitimate trust signal rather than pure filler.

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 read-only, output-schema-less search tool with 8 optional parameters, the definition covers data source, geographic coverage, and field-completeness caveats, which is enough to call it correctly. Missing pieces are minor: no indication of result volume, ordering, or behavior when filters conflict (e.g., town outside the covered region).

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 75%, so most parameters including q, lat, lon, type, radius and open_now are already documented in the schema. The description's only parameter-relevant contribution is bounding which counties/towns are valid, which meaningfully constrains the county and town filters. It adds no extra syntax or interaction detail (e.g., how lat/lon combine with radius versus town).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search manufacturer listings') sourced from the NYSLA active-license dataset, with precise geographic scope (Broome west through Erie and Niagara, Finger Lakes, Southern Tier). The title supplies the brewery/winery/cidery/distillery enumeration that the description abbreviates as 'manufacturer listings'. It does not explicitly distinguish itself from search_places or get_place, so the sibling separation must be inferred from scope alone.

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?

Implicit usage guidance comes from the coverage constraint: it only returns results for the western NY counties, which tells an agent when this is the wrong tool for other regions. However, it never names an alternative for out-of-area or non-manufacturer queries, and gives no prerequisites or exclusions beyond geography.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources