bar-assistant-mcp

Overview Schema Source Related Servers Discussions Admin

bar_list_ingredients

List and filter bar ingredients by category, name, origin, ABV, shelf status, or missing images. Use it to browse inventory and find bottles still needing artwork.

Instructions

List and filter ingredients.

For an "incomplete entries" worklist (bottles missing an image / ABV / flavor profile), prefer bar_audit_ingredients — it already scopes to real bottles and groups the gaps. Use this tool for general browsing/filtering.

Filters:

category: restrict to a category's whole subtree (recursive). Pass the category ingredient's ID — in Bar Assistant categories ARE ingredients (e.g. Rye Whiskey 347, London Dry Gin 384, Rhum Agricole 380). Returns every bottle filed anywhere under it.
name: substring match on the ingredient name.
specific_only: only specific bottles (leaf ingredients), excluding the generic category/parent ingredients themselves. NOTE: "leaf" is structural — it still includes commodity leaves (juices, syrups, produce). Add exclude_commodities for a real-bottle list.
missing_image_only: only ingredients with no image attached — use this to find bottles whose artwork still needs filling in.
exclude_commodities: drop non-bottle commodities (juices, syrups, produce, dairy, ice/salt). The combo specific_only + missing_image_only + exclude_commodities is the clean "real bottles still missing artwork" list.
on_shelf_only: only ingredients currently in the bar's inventory.
origin: substring match on origin (country/region).
strength_min / strength_max: ABV bounds (e.g. strength_min=40).
sort: "name" (default), "-name", "created_at", "strength", "total_cocktails", "-total_cocktails" (most-used first).

Output marks each ingredient's cocktail count and flags "NO IMAGE" so the list is directly actionable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`page`	No
`sort`	No
`limit`	No
`origin`	No
`category`	No
`strength_max`	No
`strength_min`	No
`on_shelf_only`	No
`specific_only`	No
`missing_image_only`	No
`exclude_commodities`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

A4.7/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 full burden, and it delivers: it explains filter semantics (recursive category, structural 'leaf' meaning, commodity exclusion) and the output behavior (cocktail counts, 'NO IMAGE' flags). It omits pagination/limit behavior and any auth or rate-limit context, keeping it short of a 5.

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?

Purpose and the sibling-routing guidance are front-loaded, then filters are cleanly bulleted one per parameter. It is long, but the length is justified by 12 undocumented parameters; a few phrasings could still be tightened.

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?

With an output schema present, the description needn't explain return values, yet it still notes the actionable output. All filtering paths an agent needs for a 12-param browse tool are covered; only pagination is unaddressed and that is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and largely does: it documents category (as an ingredient ID, with real examples), name, origin, strength_min/max, all four boolean filters, and the full set of sort enum values. Only page and limit are left undocumented, a minor gap against 10 of 12 params covered.

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 ('List and filter ingredients') and immediately distinguishes itself from the sibling bar_audit_ingredients, naming the exact scenario each serves. An agent can route between them without opening either 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 says when to prefer the alternative ('incomplete entries' worklist → bar_audit_ingredients) and when to use this one (general browsing/filtering). It also supplies concrete filter combinations, e.g. specific_only + missing_image_only + exclude_commodities for the 'real bottles missing artwork' list.

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

Deploy Server