Skip to main content
Glama

find_drink

Find venues whose VERIFIED menu lists a specific non-alcoholic drink — e.g. a real NA negroni, non-alcoholic IPA, zero-proof espresso martini, NA spritz or kava serve — optionally in one city. Every result comes from the venue's own published menu (read verbatim and dated), never from reviews or guesses, so a listed venue genuinely pours that drink. Returns the matching menu items (name, description, price where printed, on-draft flag), the menu's last-confirmed date, and the canonical nabarfinder.com URLs for citing. Drinks currently on menus (24 kinds across 625 venue-pours): na-ipa (124), na-lager (83), na-spritz (82), na-sparkling-wine (69), na-negroni (57), na-white-wine (28), kava-serve (22), na-margarita (20), na-mocktail-sour (20), na-mojito (20), na-espresso-martini (17), na-red-wine (17), na-stout (11), na-old-fashioned (9), na-paloma (8), na-gin-and-tonic (6), na-margarita-spicy (6), functional-adaptogen-cocktail (5), na-aperol-spritz (5), na-negroni-sbagliato (4), na-sour (4), na-highball (3), na-moscow-mule (3), na-wheat-beer (2). Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drink": "<drink>"
    },
    "name": "find_drink"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoLimit to one covered city — slug ('austin-tx'), name ('Austin') or 'Austin, TX'. Omit for every city.
drinkYesThe drink, as a slug ('na-negroni') or plain words ('non-alcoholic negroni', 'NA IPA', 'virgin mojito'). Unknown drinks return the catalog of known slugs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the whole burden, and it does substantial work: it declares read-only behavior, discloses the provenance rule (verbatim, dated published menus, never reviews or guesses), and describes the return payload fields and canonical URLs. Gaps remain around result caps, pagination, and whether multiple menu items per venue are returned, which matter for a query that could span 625 venue-pours.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded and states the core contract plus scope in one line. However, the trailing 24-item slug-and-count inventory consumes roughly a third of the description and is partially redundant with the schema's stated behavior of returning the catalog for unknown drinks, so not every token earns its place.

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?

With no output schema and no annotations, the description compensates well by describing the returned item shape, the confirmation date, and the citation URLs. It is nearly sufficient to call correctly; only result-volume behavior (limits/pagination) is left unstated.

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 100%, so both parameters are already documented in the schema, and the description adds only modestly on the city argument. It does add real value for 'drink' by listing the actual slug vocabulary (na-ipa, na-negroni, kava-serve, etc.) with pour counts, which the schema lacks via enums — but the list is presented as marketing context rather than as an explicit enumeration of accepted values.

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 and resource — 'Find venues whose VERIFIED menu lists a specific non-alcoholic drink' — plus the optional city scoping. This is clearly distinguishable from siblings like get_menu (one venue's full menu) or search_venues (venue-level search), since the unit of search here is a menu item.

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?

The when-to-use context is clear: you have a specific NA drink in mind and want venues that actually pour it, optionally narrowed to a city. It also explains the fallback path for unknown drink inputs (returns the known-slug catalog). It stops short of explicitly naming alternatives such as get_menu or search_venues and when to prefer them.

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