Skip to main content
Glama

Cocktailline

Rezept abrufen

get_recipe
Read-only

Returns a full cocktail recipe (ingredients with amounts, steps, glass, history) as Markdown, plus the link to the recipe page with photo, party calculator and ratings.

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": {
      "cocktail": "<cocktail>"
    },
    "name": "get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
cocktailYesCocktail name or slug, e.g. "Mojito"
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so safety is already covered, and the description adds real value by disclosing the return shape (Markdown recipe plus a page link/ratings). It does not mention error behavior for an unknown cocktail or any locale-related behavior, but with annotations carrying the safety profile this is solid.

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 front-loaded sentence with no filler; the content list is dense but each item earns its place by telling the agent what comes back. Only slight overloading from the long parenthetical.

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 no output schema, the description usefully describes the return payload and format, which is the main thing an agent needs. Gaps remain around the language parameter's behavior and what happens when the named cocktail does not exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'cocktail' is documented with an example, but the 'language' enum (de/en/fr/es) has no description in the schema. The description never mentions parameters at all, so it fails to compensate for the undocumented language parameter or explain its effect on output.

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 (returns) and resource (full cocktail recipe) and enumerates the payload (ingredients with amounts, steps, glass, history, link to page with photo, party calculator, ratings). This clearly separates it from search/find siblings, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the detail-retrieval step after search_cocktails/find_cocktails. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance is minimal but derivable from context.

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.

Resources