Skip to main content
Glama

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).

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": {
      "query": "margarita"
    },
    "name": "search_cocktails"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCocktail name or partial name to search for

Output Schema

NameRequiredDescriptionDefault
countYesNumber of cocktails found
cocktailsYesList of matching cocktails

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 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"
      +}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "margarita"
      +  },
      +  {
      +    "query": "mojito"
      +  }
      +]
  3. First observed

TDQS

A4/5.0
Behavior3/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. The description adds one genuinely useful behavioral fact, that no preparation instructions are returned, but the rest of the sentence enumerates return fields that the existing output schema already provides, and it says nothing about rate limits, API key needs, or no-match behavior.

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 with zero filler, front-loaded with the verb and data source, and the sibling reference is placed at the end as a follow-on action. Every clause carries information.

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?

With an output schema present, the description need not explain return values, and it correctly covers scope plus the key limitation. The only minor gap is that no-match or empty-result behavior for a name search, a known quirk of this API, is left unstated.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that it takes a cocktail name or partial name. The description's phrase "by name" adds no syntax or matching detail beyond that, 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 and resource ("Search TheCocktailDB for cocktail recipes by name") plus the scope (name matching). It also distinguishes itself from get_cocktail by naming that sibling as the route for preparation instructions, so an agent can pick between them 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?

Clearly establishes the lookup-by-name use case and explicitly routes an agent to get_cocktail when preparation instructions are needed, which is a concrete exclusion. It gives no guidance on when to prefer cocktails_by_ingredient or random_cocktail, but the stated condition is enough for the common decision.

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.