Skip to main content
Glama

cocktail_get_by_id

Read-onlyIdempotent

Retrieves a cocktail or drink record from TheCocktailDB using its unique ID, returning details for a specific beverage.

Instructions

Get a cocktail/drink by ID.

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": {
      "id": "<id>"
    },
    "name": "cocktail_get_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTheCocktailDB drink ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/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 fully covered. The description adds nothing beyond that — no note on what happens with an invalid ID, whether the response is a single object, or how it differs from random/search lookups.

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 no filler. It is efficient but borders on under-specified rather than lean.

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 rich annotations, full schema coverage, and only one parameter, the description is close to sufficient for calling the tool. It stops short on return shape (no output schema exists, so a sentence about the drink record would help) and on error behavior for a missing ID.

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 documents the single 'id' parameter at 100% coverage as the TheCocktailDB drink ID, and the description adds no format, example, or validation detail. Baseline 3 applies because the schema carries all parameter meaning.

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 ('Get a cocktail/drink by ID'), and the 'by ID' qualifier implicitly separates it from search-style siblings. It does not explicitly name cocktail_search or cocktail_random, so an agent must infer the distinction from the name alone.

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 when-to-use, when-not-to-use, or alternative routing is given. The agent is left to guess that this is the right tool when it already holds an ID rather than a name or category, which the sibling set (cocktail_search, cocktail_filter_by_category, cocktail_filter_by_ingredient) makes a real ambiguity.

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