foodos-mcp

parseRecipe

Read-onlyIdempotent

Extract a recipe's title, ingredients, servings, and instructions from any web page using its structured data. Returns clear errors when no schema.org markup exists, so you know the page lacks machine-readable recipe info.

Instructions

Read a recipe from a web page. Returns its title, ingredient lines as written, declared servings and instructions, taken from the schema.org data the page publishes for machines. Fails clearly when a page has no structured data rather than guessing at the markup.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL of a recipe page.

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes
`author`	Yes
`finalUrl`	Yes
`fromCache`	Yes
`sourceUrl`	Yes
`instructions`	Yes
`ingredientLines`	Yes
`declaredServings`	Yes	The first integer found in the page's recipeYield, or null. This is the author's claim about servings, not a measured household portion, and is never guessed.
`extractionMethod`	Yes
`declaredYieldText`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description reveals that data comes specifically from schema.org structured data and that the tool fails clearly rather than guessing when no structured data exists. This is valuable behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the core action, and every sentence earns its place. It covers what the tool does, what it returns, and its failure behavior without redundancy.

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?

For a single-parameter tool with an output schema, the description is complete: it specifies the input, the source of the data, the returned fields, and the failure mode. No additional guidance is needed for correct invocation.

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 already covers the single url parameter at 100% with a clear description and format. The tool description reinforces that it should be a public recipe web page, but does not add significant meaning beyond the schema, so it meets the baseline.

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 names a specific verb and resource: reading/parsing a recipe from a web page. It also specifies exactly what is returned (title, ingredient lines, servings, instructions), which distinguishes it clearly from siblings like parseIngredientLine.

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 context: use this when you have a recipe URL and need machine-readable structured data from the page. It does not name alternatives or explicitly state when not to use it, but the context is strong enough to guide selection among siblings.

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

Deploy Server