Skip to main content
Glama
smeet666

mcp-recipes

Read one recipe, optionally rescaled

get_recipe
Read-onlyIdempotent

Read a full recipe by its source ID: ingredients, steps, yield, times, rating, and nutrition. Rescale quantities to any serving count and return only the sections you select.

Instructions

Read one recipe in full: its ingredients, its steps, what it yields, and whatever times, rating and nutrition its source publishes. 'id' must come from search_recipes. It names the source, so this reads the right one without guessing; an identifier no source would have minted is refused, because sending it anywhere would answer about the wrong dish. Pass 'servings' to rescale. Quantities land where a kitchen can follow them: an egg stays whole, anything that pours or cuts can halve, a small measurement moves to a smaller unit before it is rounded, and anything unmultipliable is flagged rather than scaled. A page that states no number of servings comes back as published and says so, because dividing by a yield nobody wrote would answer for a number of people the page never claimed. A part this answer holds nothing for says which of two things happened: the page showed no sign of it, or this server failed to read what the page carries. An empty ingredient list is never evidence that an ingredient is absent from the dish. 'sections' decides what comes back, and 'sections_omitted' names what was left out: a field belonging to an omitted section is empty because nobody asked for it, never because the page states nothing. A field a source does not publish is null, never zero. Credit the source and link the url when you repeat any of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFrom search_recipes, such as 'marmiton:44078', 'goodfood:recipes/carbonara' or 'cookbook:Cookbook:Carbonara'. Two sources address a recipe by a bare number, so spell an id with its source.
sectionsNoWhich parts to return. A full recipe is a lot of text, so this defaults to two.
servingsNoRescale to this many. Left out, the quantities come back as published.
max_stepsNoSteps to return. The answer says how many more there are.
max_step_charsNoCharacters kept per step. Raise it only if a step was cut mid-sentence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
recipeYes
id_read_asYesHow a raw identifier was routed, when it was not spelled with its source.
Behavior5/5

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

The description goes far beyond the annotations by disclosing detailed behavioral edge cases: rescaling rules (eggs stay whole, pours/cuts may halve, unmultipliable fields are flagged), behavior when no serving count is published, how absent sections are reported, the meaning of empty ingredient lists, and the null-versus-zero convention. These are exactly the caveats an agent needs to interpret results correctly.

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?

The description is long but well-structured: the core purpose is front-loaded, followed by id provenance, rescaling behavior, and result interpretation rules. Each sentence contributes a distinct behavioral or usage nuance. A few sentences could be tightened, but for a tool with this many edge cases the length is justified.

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?

Given the rich output schema and annotations covering read-only, idempotent, and non-destructive behavior, the description covers everything an agent needs to call the tool correctly and interpret its results: identity constraints, rescaling semantics, section omission behavior, null-versus-zero conventions, and the significance of empty ingredient lists. No critical information is missing.

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 100%, and each parameter already has a detailed description with defaults and constraints. The tool description adds minimal parameter-level meaning beyond the schema, mostly restating that servings triggers rescaling and sections selects output. This matches the baseline of 3 for high schema coverage.

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?

The description opens with a specific verb and resource ('Read one recipe in full') and enumerates what is returned: ingredients, steps, yield, times, rating, nutrition. It also differentiates from the sibling search_recipes by requiring that 'id' come from it, so there is no ambiguity about which tool does what.

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?

The description gives clear operational guidance: the id must originate from search_recipes, servings can be passed to rescale, and sections controls what is returned. It also explains why unknown ids are refused. It does not explicitly name when to prefer a sibling such as scale_ingredients or compare_recipes, but the context is strong enough that an agent will know when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-recipes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server