bar-assistant-mcp

Overview Schema Source Related Servers Discussions Admin

bar_list_cocktails

List and filter cocktails by name, favorites, tag, ingredient, method, glass, collection, ABV, or missing images; sort and page through results for browsing or auditing.

Instructions

List and filter cocktails. Use to browse or audit the collection.

Filters:

name: substring match on the cocktail name.
favorites_only: only favorited cocktails.
tag_id / ingredient_id / method_id / glass_id / collection_id: restrict by tag, an ingredient used, prep method, glass, or collection (IDs from the matching list_* tools).
parent_cocktail_id: only variants/riffs of a given cocktail.
abv_min / abv_max: ABV bounds.
missing_image_only: only cocktails with no image attached (audit helper).
sort: "name" (default), "-name", "abv", "-abv", "average_rating", "total_ingredients", "created_at", "random".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`page`	No
`sort`	No
`limit`	No
`tag_id`	No
`abv_max`	No
`abv_min`	No
`glass_id`	No
`method_id`	No
`collection_id`	No
`ingredient_id`	No
`favorites_only`	No
`missing_image_only`	No
`parent_cocktail_id`	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

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It hints at read-only listing via 'browse or audit' and clarifies the missing_image_only audit helper, but does not state safety profile, pagination semantics, or how page/limit interact. It is helpful but not rich.

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?

Front-loads the purpose in one sentence, then a clean bulleted filter list. The bullets largely mirror schema keys, so there is mild redundancy, but each line maps to undocumented behavior or enum values.

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 14-parameter filter tool with no annotations and an output schema, the description supplies the missing filter semantics and sort options. It leaves pagination (page/limit) implicit, a minor gap given the output schema covers returns.

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 description coverage is 0%, so the description must compensate. It explains the meaning of nearly every filter and even gives sort enum values and ID provenance ('from the matching list_* tools'). It omits only page and limit semantics.

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+resource ('List and filter cocktails') and adds a scope note ('browse or audit the collection'). It doesn't explicitly differentiate from siblings like bar_search_cocktails or bar_makeable_cocktails, which an agent must infer.

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?

Says to use it 'to browse or audit the collection,' which distinguishes auditing (via missing_image_only) from browsing, but gives no explicit when-not or contrast with similar siblings such as search_cocktails or makeable_cocktails.

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

Deploy Server