cocktails

Cocktails By Ingredient

cocktails_by_ingredient

Read-onlyIdempotent

List all TheCocktailDB cocktails that contain a specific ingredient (e.g., 'vodka', 'lime juice'). Returns cocktail id, name, and thumbnail only — use get_cocktail to retrieve full recipes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ingredient`	Yes	Ingredient name to filter by (e.g., "vodka", "gin")

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of cocktails found
`cocktails`	Yes	List of cocktails containing the ingredient
`ingredient`	Yes	Ingredient searched for

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cocktails": {
+      "description": "List of cocktails containing the ingredient",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Cocktail ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Cocktail name",
+            "type": "string"
+          },
+          "thumbnail": {
+            "description": "Thumbnail image URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "thumbnail"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of cocktails found",
+      "type": "integer"
+    },
+    "ingredient": {
+      "description": "Ingredient searched for",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ingredient",
+    "count",
+    "cocktails"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "ingredient": "vodka"
+  },
+  {
+    "ingredient": "lime juice"
+  }
+]

First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds context by stating it returns only cocktail id, name, and thumbnail, and that it lists 'all' cocktails, which clarifies scope beyond the annotations. No contradiction is present.

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?

Two concise sentences: first states the primary action and examples, second clarifies return fields and points to an alternative. No wasted words, information is front-loaded and directly useful.

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?

The tool is simple (one parameter, no nested objects) and has an output schema. The description covers the essential behavior and return scope, while the output schema handles return values. The alternative for full recipes is also mentioned, making it fully complete.

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% with a clear description of the 'ingredient' parameter. The description provides examples (e.g., 'vodka', 'lime juice') but does not add meaning beyond the schema, which already explains the parameter. Baseline 3 is appropriate.

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 lists all TheCocktailDB cocktails containing a specific ingredient, with a specific verb and resource. It also distinguishes itself from the sibling get_cocktail by noting it returns only id, name, and thumbnail, making the purpose unambiguous.

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?

The description explicitly tells the agent when to use this tool (to list cocktails by ingredient) and when to use an alternative ('use get_cocktail to retrieve full recipes'). This provides clear guidance on selecting between related tools.

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

All cocktails tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.