Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingredient": "vodka"
    },
    "name": "cocktails_by_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
ingredientYesIngredient name to filter by (e.g., "vodka", "gin")

Output Schema

NameRequiredDescriptionDefault
countYesNumber of cocktails found
cocktailsYesList of cocktails containing the ingredient
ingredientYesIngredient searched for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ingredient": "vodka"
      +  },
      +  {
      +    "ingredient": "lime juice"
      +  }
      +]
  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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds real value by disclosing the truncated result shape ('id, name, and thumbnail only'), which warns the agent not to expect recipe detail from this call.

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 sentences, zero filler: the capability and its scope come first, the follow-up routing sentence second. Every clause carries information the agent needs.

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?

A single-parameter lookup with full annotation coverage and an output schema in place; the description supplies the purpose, the result truncation, and the next-step tool. Nothing required for correct invocation is missing.

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 description coverage is 100% and the schema already carries examples (vodka, lime juice) identical to those in the description. The description adds no syntax or matching rules beyond the schema (e.g., free-text vs. exact match), so baseline 3 applies.

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 (List) and resource (TheCocktailDB cocktails containing a given ingredient), plus the scope limitation that only id, name, and thumbnail come back. It explicitly contrasts itself with the sibling get_cocktail, so an agent can separate the two 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 Guidelines4/5

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

Routes the agent onward with 'use get_cocktail to retrieve full recipes,' which is a clear when-to-use-this-vs-that signal. It lacks an explicit inverse statement (e.g., when to use search_cocktails versus this) and no negative conditions, keeping it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.