Skip to main content
Glama
smeet666

mcp-wikibooks-cookbook

Read a recipe

get_recipe
Read-onlyIdempotent

Read a complete Wikibooks Cookbook recipe: ingredients, steps, yield, time, difficulty, and nutrition. Optionally rescale ingredient quantities to a desired number of servings.

Instructions

Read one Wikibooks Cookbook page: ingredients, equipment, steps, yield, time, difficulty, category, and the nutrition panel when the page carries one. 'id' is the page key from search_recipes or list_recipes, such as 'Cookbook:Spaghetti_alla_Carbonara'. A plain dish name is accepted and the Cookbook namespace is added. Pass 'servings' to rescale: countable things land on whole or half units, a measurement is moved to a smaller unit before rounding so nothing disappears, and anything that cannot be multiplied is flagged instead. Read 'scaling' on each ingredient rather than doing the arithmetic yourself. Rescaling needs a yield to scale from. A page that states none comes back as published, and says so. A page yielding no quantities is answered with 'factor' 1 and a note: an empty ingredient list was multiplied by nothing. 'author' and 'rating' are always null: the Cookbook is written collectively and carries no reader score. A time the page does not state is null, never zero, and never inferred from the steps. Pages are published under a licence that requires attribution; 'license' and 'url' carry what to credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPage key from a search, such as 'Cookbook:Spaghetti_alla_Carbonara'.
servingsNoRescale the ingredients to this many servings.
max_description_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlYes
tipsYesNotes, tips and variations the page publishes.
notesYes
stepsYes
titleYes
yieldYes
authorYesAlways null: the Cookbook is written collectively.
energyYesEnergy per serving as the page states it.
ratingYesAlways null: the Cookbook carries no reader score.
sourceYes
licenseYes
categoryYes
equipmentYes
nutritionYes
time_textYesThe time in the page's own wording.
categoriesYesEvery category the page files itself under.
difficultyYes
revised_atYes
attributionYes
descriptionYes
ingredientsYes
cook_minutesYes
prep_minutesYes
total_minutesYes
difficulty_maxYesThe scale 'difficulty' sits on.
Behavior5/5

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

Despite strong annotations (readOnlyHint, openWorldHint, idempotentHint), the description adds substantial non-obvious behavior: null author/rating, time null handling, license attribution requirements, rescaling edge cases, and the 'factor 1' empty-quantity response. This goes far beyond what annotations convey.

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 longer than average but every sentence carries unique information about behavior, edge cases, or constraints. It is well-organized: starting with the core read operation, then parameter behaviors, then null-handling and attribution. It earns its length but could be tightened.

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 tool's complexity (rescaling, multiple null/edge cases, licensing) and that an output schema exists, the description covers all important usage aspects. It explains how to identify recipes, how rescaling behaves, what is always null, and what needs attribution, making it sufficient for safe and correct invocation.

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?

The schema already provides descriptions for all three parameters, giving a high coverage baseline. The description enriches 'id' with namespace-adding behavior and 'servings' with detailed rescaling semantics (whole/half units, unit conversion, flagging non-multipliable items), which meaningfully surpass the schema.

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 'Read one Wikibooks Cookbook page' and enumerates the exact contents (ingredients, equipment, steps, yield, time, difficulty, category, nutrition panel). This clearly distinguishes the tool from siblings like search_recipes/list_recipes and even addresses the rescale capability relative to scale_ingredients.

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 tells the agent to obtain 'id' from search_recipes or list_recipes, and explains when to use the built-in rescaling. It does not explicitly contrast with the scale_ingredients sibling, so there is room to clarify when to prefer this tool's servings parameter over the dedicated scaling 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-wikibooks-cookbook'

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