Skip to main content
Glama

cocktails

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Cocktail

get_cocktail
Read-onlyIdempotent

Get full cocktail recipe by ID. Returns ingredients with exact measurements, preparation steps, glassware type, and garnish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTheCocktailDB cocktail ID (e.g., "11007")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCocktail ID
nameYesCocktail name
glassYesGlassware type
categoryYesDrink category
alcoholicYesAlcoholic status
thumbnailYesThumbnail image URL
ingredientsYesList of ingredients with measurements
instructionsYesPreparation instructions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "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 with measurements",
+      "items": {
+        "properties": {
+          "ingredient": {
+            "description": "Ingredient name",
+            "type": "string"
+          },
+          "measure": {
+            "description": "Measurement/quantity",
+            "type": "string"
+          }
+        },
+        "required": [
+          "ingredient",
+          "measure"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "instructions": {
+      "description": "Preparation instructions",
+      "type": "string"
+    },
+    "name": {
+      "description": "Cocktail name",
+      "type": "string"
+    },
+    "thumbnail": {
+      "description": "Thumbnail image URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "category",
+    "alcoholic",
+    "glass",
+    "instructions",
+    "thumbnail",
+    "ingredients"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "11007"
+  },
+  {
+    "id": "11003"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the exact content of the returned recipe, which goes beyond the structured fields.

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?

The description is a single, information-dense sentence with zero wasted words. It front-loads the core purpose and lists specifics concisely.

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 a single parameter, clear annotations, and an output schema present, the description covers the essential context. It states what the tool returns and implies when to use it, making it fully adequate for selecting and invoking.

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 schema has 100% coverage for the single 'id' parameter, so the baseline is 3. The description adds only 'by ID' which repeats the schema, providing no additional semantic meaning.

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 verb 'Get' and the resource 'full cocktail recipe by ID', specifying return content (ingredients, measurements, steps, glassware, garnish). This distinguishes it from siblings like random_cocktail or 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used when you have a cocktail ID, providing clear context. It does not explicitly name alternatives, but the 'by ID' scope makes it obvious when to use it versus search or random.

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

All cocktails toolsInspect
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.

Resources