Agent Chef

Get a recipe

get_recipe

Read-only

Retrieve one recipe's full details by recipe ID: ingredients, steps, servings, ratings, comments, and a public share URL.

Instructions

Full details for one recipe: ingredients, steps, servings, source, tags, ratings, comments, how often it's been cooked, a link to its page, and a public share_url anyone can open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`recipe_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`tags`	No
`steps`	No
`title`	Yes
`ratings`	No
`comments`	No
`servings`	No
`image_url`	No
`is_public`	No
`on_ballot`	No
`share_url`	No	Public page for this recipe
`avg_rating`	No
`created_at`	No
`public_url`	No	Indexable public page, when published
`source_url`	No
`description`	No
`ingredients`	No
`is_favorite`	No
`last_cooked`	No
`rating_count`	No
`times_cooked`	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.

Changed5 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 / share_url

Added value: +{
+  "description": "Public page for this recipe",
+  "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

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds only a return-content inventory, which is largely redundant given an output schema exists; it says nothing about auth, not-found behavior, or rate limits. Beyond what annotations provide, the added behavioral context is minimal, though it does disclose that a public share_url is exposed.

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?

One sentence, front-loaded with 'Full details for one recipe' before the field list. The list is long but each item earns its place by telling the agent what is retrievable; the trailing share_url clause is a marginally useful addition.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with annotations and an output schema, the definition is essentially complete — the agent knows what it fetches and that it is a non-destructive read. Only the recipe_id resolution and not-found handling are unaddressed, which is a minor gap given the output schema carries the return shape.

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 0%, but there is a single self-explanatory recipe_id (string, required), and the description's 'one recipe' framing supplies the identifier semantics implicitly. No format, source, or lookup guidance for the id is given, so no credit above 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?

States a specific verb and resource ('Full details for one recipe') and enumerates exactly what the payload contains, which cleanly separates it from search_recipes, update_recipe, and get_recipe_preferences. An agent can identify the tool's job without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — fetch the complete record for a recipe you already have an id for — but there is no explicit when-to-use vs. alternatives (e.g., search_recipes for discovery, get_recipe_preferences for prefs) and no stated prerequisites or failure modes for a missing recipe_id.

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