Skip to main content
Glama

cocktail_ingredient_info

Read-onlyIdempotent

Retrieve a cocktail ingredient's description, type, and ABV to identify and evaluate ingredients for recipes or bar workflows.

Instructions

Get details about a cocktail ingredient (description, type, ABV).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingredient": "<ingredient>"
    },
    "name": "cocktail_ingredient_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
ingredientYesIngredient name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the result is an ingredient record with description/type/ABV, which is useful, but it says nothing about how an unknown ingredient name is handled or that lookups hit an external service.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the verb and resource, with the payload spelled out in parentheses. No waste, though it is terse enough that it under-informs rather than over-informs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does partially compensate by naming the returned fields. For a simple one-param lookup this is close to adequate, but the omission of failure behavior for unrecognized ingredients leaves a real gap for an openWorld tool.

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 parameter with 100% schema description coverage, so the schema already carries the meaning. The description adds nothing about accepted name formats (case sensitivity, brand names, synonyms), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Get details about') plus specific resource ('a cocktail ingredient') and even enumerates the returned fields (description, type, ABV). It does not, however, distinguish itself from siblings like cocktail_by_ingredient or cocktail_filter_by_ingredient, which sound similar enough that an agent could pick the wrong one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No indication of when to use this versus cocktail_by_ingredient (ingredient-to-cocktails) or cocktail_search. The agent must infer the distinction from the name alone, and no exclusions or prerequisites are stated.

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

Deploy Server

Other Tools