Skip to main content
Glama

cocktail_search

Read-onlyIdempotent

Find cocktails and drinks by name to quickly retrieve matching beverage results.

Instructions

Search for cocktails/drinks by name.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/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 only the name-matching angle and does not disclose whether matching is substring or exact, whether results are capped, or how ranked/ordered — small but real gaps given the bar is lower 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.

Conciseness4/5

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

A single short sentence with the search key front-loaded and nothing redundant. It is efficient, though so terse that it borders on under-specification rather than tight completeness.

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?

For a one-parameter, read-only lookup with annotations and no output schema, this is close to the minimum viable. Missing are match semantics and result behavior, which an agent would want before choosing this over cocktail_get_by_id or the ingredient filters.

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 0% with one required string 'query', so the schema provides only a bare name. The description maps query to a cocktail/drink name, which is modest but genuine added meaning; it does not clarify casing, partial-match, or multi-word handling.

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?

States a specific verb and resource ('Search for cocktails/drinks') plus the matching key ('by name'), which lets an agent separate it from cocktail_filter_by_category and cocktail_filter_by_ingredient. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'By name' implies the precondition that the caller already has a drink name, but there is no explicit when-to-use or when-not-to-use guidance against the five other cocktail tools (cocktail_random, cocktail_get_by_id, cocktail_filter_by_category, cocktail_filter_by_ingredient, cocktail_by_ingredient). Usage is implied, not 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