Skip to main content
Glama

Get a recipe

get_recipe
Read-onlyIdempotent

Use this when the user wants to see or cook one specific recipe: its ingredients, steps, times and photo. Pass servings to scale every ingredient quantity. Takes an id or slug from another tool's results; for a pasted link use import_recipe. Without a linked account the recipe comes from the public recipe page's data: a few internal columns (video ids, short title, SEO title, bookmark/favorite/collection counts, site, cuisine and restaurant refs) come back null.

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

Input Schema

NameRequiredDescriptionDefault
servingsNoScale the ingredients to this many servings. Leave out for the recipe as written.
identifierYesThe recipe slug or ID (IDs start with 'rec_')

Output Schema

NameRequiredDescriptionDefault
recipeNo
statusNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so this dimension has a lower bar. The description clears it by disclosing that without a linked account, several internal fields (video ids, short title, SEO title, counts, site, cuisine, restaurant refs) return null, giving the agent real context about data dependence on account state.

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?

All three sentences carry information, and the primary trigger plus the import_recipe alternative are front-loaded. The final sentence is dense and packed with a long parenthetical list of nullable columns, which slightly hurts scannability but is still informative rather than wasteful.

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

Completeness5/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 needn't explain return values, and it instead covers triggers, identifier sourcing, the scaling parameter, and the token nuance of auth-dependent nulls. For a two-parameter read tool with full annotations, nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by stating that servings scales 'every ingredient quantity' and by describing where the identifier originates and its 'rec_' ID format, which helps the agent source valid input.

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 ('see or cook one specific recipe') along with the payload it returns (ingredients, steps, times, photo). It also distinguishes itself from import_recipe by routing pasted links there, so an agent can tell single-recipe retrieval apart from the siblings without opening a 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?

Gives an explicit trigger ('when the user wants to see or cook one specific recipe') and a concrete exclusion with the alternative named ('for a pasted link use import_recipe'). It also says where the identifier comes from (another tool's results, IDs starting with 'rec_'). It does not explicitly say when to use find_recipe or search_recipes to obtain an identifier, which is a minor gap.

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