cocktails

Search Cocktails

search_cocktails

Read-onlyIdempotent

Search TheCocktailDB for cocktail recipes by name. Returns name, category, alcoholic/non-alcoholic classification, glassware, thumbnail, and ingredient list with measurements (no preparation instructions — use get_cocktail for those).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Cocktail name or partial name to search for

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of cocktails found
`cocktails`	Yes	List of matching cocktails

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 matching cocktails",
+      "items": {
+        "properties": {
+          "alcoholic": {
+            "description": "Alcoholic status",
+            "type": "string"
+          },
+          "category": {
+            "description": "Drink category",
+            "type": "string"
+          },
+          "glass": {
+            "description": "Glassware type",
+            "type": "string"
+          },
+          "id": {
+            "description": "Cocktail ID",
+            "type": "string"
+          },
+          "ingredients": {
+            "description": "List of ingredients",
+            "items": {
+              "properties": {
+                "ingredient": {
+                  "description": "Ingredient name",
+                  "type": "string"
+                },
+                "measure": {
+                  "description": "Measurement/quantity",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "ingredient",
+                "measure"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Cocktail name",
+            "type": "string"
+          },
+          "thumbnail": {
+            "description": "Thumbnail image URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "alcoholic",
+          "glass",
+          "thumbnail",
+          "ingredients"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of cocktails found",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "cocktails"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "margarita"
+  },
+  {
+    "query": "mojito"
+  }
+]

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 no destructive action, so the safety profile is covered. The description adds meaningful context: it returns a limited set of fields and explicitly excludes preparation instructions, which is a behavioral constraint an agent would need to know. No contradiction with annotations.

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, front-loaded with the primary purpose. The first sentence states the action, the second gives return fields and a key limitation with an alternative. No wasted words.

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?

For a simple one-parameter search tool with a rich output schema and annotations, the description covers the purpose, return fields, an important exclusion (prep instructions), and names the alternative. It is complete enough for an agent to decide when and how to use it.

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?

The input schema fully covers the parameter with a clear description ('Cocktail name or partial name to search for'), so the description doesn't need to add much. The tool description merely echoes 'by name' without adding extra detail, giving baseline value.

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 searches TheCocktailDB by name, which is a specific verb+resource combination. It distinguishes from siblings by noting the lack of preparation instructions and directing to get_cocktail for those, and the phrase 'by name' implicitly contrasts with cocktails_by_ingredient.

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?

It explicitly states when not to use this tool ('no preparation instructions') and names the alternative (get_cocktail). The 'by name' scope also implies it's for name-based searches, not ingredient-based ones, providing clear guidance for selecting among sibling 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.