Agent Chef

Import a recipe from a URL

import_recipe

Fetch a recipe URL and save its real photo, ingredients, and steps to your Agent Chef library; then use the returned recipe ID for meal-planning ballots.

Instructions

Fetch a recipe page (most cooking sites) and save it to the library with its real photo, ingredients, and steps. Returns the recipe; pass its recipe_id to propose_recipes or add_candidates to put it on a ballot.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`tags`	No	Extra tags to add
`favorite`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`tags`	No
`steps`	No
`title`	Yes
`servings`	No
`image_url`	No
`is_public`	No
`created_at`	No
`public_url`	No	Indexable public page, when published
`source_url`	No
`description`	No
`ingredients`	No
`is_favorite`	No
`total_minutes`	No
`image_generated`	No	Photo was generated by Agent Chef, so it is safe to show publicly
`source_recipe_id`	No	Set when this is the household's copy of a Community recipe

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 3, 2026

addedOutput schema / properties / image_generated

Added value: +{
+  "description": "Photo was generated by Agent Chef, so it is safe to show publicly",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / is_public

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / public_url

Added value: +{
+  "description": "Indexable public page, when published",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / source_recipe_id

Added value: +{
+  "description": "Set when this is the household's copy of a Community recipe",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedv0.1.0Sep 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations cover openWorldHint (external fetch) and destructiveHint=false, but the description adds meaningful context: it fetches from cooking sites, saves with the 'real' photo (implying image retrieval), and returns the recipe. Does not address failure modes or permissions, but the network-fetch implication is useful.

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?

Two tight sentences, front-loaded with the action and result, followed by a routing hint. No filler.

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 3-parameter import tool with an output schema, the description covers purpose, effect, and downstream usage. An agent has everything needed to invoke and chain it.

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 only 33% – url and favorite lack descriptions – but the description clarifies the url is the source page and implies downstream use via recipe_id (output). It doesn't explain tags or favorite semantics, but adds real value over the sparse 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?

States a specific verb and resource ('Fetch a recipe page ... and save it to the library'), names what gets captured (photo, ingredients, steps), and explicitly names sibling tools (propose_recipes, add_candidates). Clear differentiation from add_library_recipe/create_recipe by emphasizing URL fetching.

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?

Clear context for use – import from a URL – and names downstream tools to route the returned recipe_id to. Lacks explicit when-not guidance (e.g., when to use create_recipe or add_library_recipe instead), which keeps it from a 5.

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