Skip to main content
Glama

Generate Recipe Prompt

generate_recipe
Read-onlyIdempotent

Returns a recipe schema and a bounded host-model prompt to synthesize a full recipe once sensory analysis, substitutions, and sourcing are ready.

Instructions

Return the expected recipe schema and a bounded host-model prompt for final recipe generation. Returns a recipe schema template and a promptForAgent for the host model to synthesize the recipe. Use when the minimum viable nostalgia cue has been shown and the user wants a full recipe. Pass sensoryAnalysis from analyze_nostalgic_dish, substitutions from find_sensory_substitutes, and sourcing from source_ingredients.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dishDescription": "<dishDescription>",
      "location": "<location>",
      "sensoryAnalysis": "<sensoryAnalysis>",
      "substitutions": "<substitutions>",
      "sourcing": "<sourcing>"
    },
    "name": "generate_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesUser's location
sourcingYesCompleted sourcing guide from source_ingredients
substitutionsYesCompleted substitutions from find_sensory_substitutes
dishDescriptionYesThe user's original dish description
sensoryAnalysisYesCompleted sensory analysis from analyze_nostalgic_dish

Output Schema

NameRequiredDescriptionDefault
locationYes
promptForAgentYes
dishDescriptionYes
expectedOutputSchemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

The readOnly/idempotent/non-destructive annotations already establish the safety profile, and the description adds the key behavioral fact that output is a bounded prompt plus schema for the host model to synthesize — not a finished recipe. It does not cover failure behavior (e.g., what happens with incomplete upstream payloads), which keeps it below a 5.

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?

Front-loaded with the return contract, then the trigger, then the parameter provenance — a logical order. The first two sentences restate the same idea ('expected recipe schema and a bounded host-model prompt' / 'a recipe schema template and a promptForAgent'), which is minor redundancy but not harmful.

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?

An output schema exists, so return values need no explanation, and the description correctly focuses on inputs and sequencing for a tool with five required nested parameters. What is missing is minor: nothing about what to do if an upstream artifact is partial or stale.

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 100% and every nested object is described in the schema, so the baseline is 3. The description goes beyond it by mapping each required parameter to the sibling tool that produces it (sensoryAnalysis ← analyze_nostalgic_dish, substitutions ← find_sensory_substitutes, sourcing ← source_ingredients), which is real added meaning.

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?

Names a specific verb and two specific artifacts ('recipe schema template' and 'promptForAgent') and makes clear this tool does not itself write the recipe — the host model does. That distinguishes it cleanly from generate_minimum_viable_nostalgia and validate_recipe_output without the agent needing to open 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 Guidelines5/5

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

Explicitly states the trigger ('when the minimum viable nostalgia cue has been shown and the user wants a full recipe') and names the three upstream tools that must run first. This is precise when-to-use and prerequisite guidance rather than implied context.

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