Skip to main content
Glama

Reconstruct Food Memory

reconstruct_food_memory

Reconstruct an incomplete food or drink memory in one call by collecting details, researching the dish, building an evidence dossier, and returning a nostalgia cue with a Memory Receipt.

Instructions

Run the full Achiote food-memory reconstruction workflow in one call: collect the memory, research and resolve the dish, build the evidence dossier, and return a minimum viable nostalgia cue with a Memory Receipt. Returns structured output with the synthesized reconstruction prose, status, tools run, and a Memory Receipt. Use when the user wants a complete reconstruction in a single call; use the granular tools only when driving individual steps. Pass memory from the user raw food or drink memory, optionally history for context and userLocation for sourcing.

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": {
      "memory": "<memory>"
    },
    "name": "reconstruct_food_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoryYesThe raw food or drink memory to reconstruct: place, people, smell, texture, packaging, cooking method, occasion, or any sensory fragment.
historyNoOptional prior turns of the conversation, oldest first, for follow-up clarification.
userLocationNoOptional current location used for sourcing and locally-available substitutes.

Output Schema

NameRequiredDescriptionDefault
answerYesThe synthesized, warm, food-science-grounded reconstruction prose for the user.
statusNoMemory Receipt status: whether more clues are needed, a first taste test is ready, or it is ready for recipe handoff.
guardedNoSet when a deterministic guard path produced the answer (e.g. minimum_cue_deterministic_completion).
receiptNoThe full Achiote Memory Receipt: evidence ledger, hypotheses, next questions, and the first tiny taste test.
toolsRunYesThe workflow tools that actually executed, in order, e.g. collect_food_memory, plan_dish_research, generate_minimum_viable_nostalgia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior3/5

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

The annotations already disclose readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful context that this is a multi-step workflow involving research, but it does not warn that repeated calls may yield different results (non-idempotent), nor does it mention latency, external calls, or any persistence/write side effects.

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 front-loaded with the workflow and its usage rule, and most sentences are efficient. The return-value sentence is somewhat redundant because an output schema exists, but it does not obscure the core instruction.

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

Completeness3/5

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

For a complex, open-world, non-idempotent multi-step workflow, the description covers the major steps and routing well. However, it omits important operational context such as the implications of non-idempotency, likely latency/cost of the research workflow, and any write or persistence behavior beyond the annotations.

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 100%, so the heavy lifting is already done structurally. The description restates that memory is the raw food or drink memory and that history/userLocation are optional, which matches the schema but adds little new meaning beyond what is already documented.

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 workflow and enumerates its steps (collect memory, research/resolve dish, build dossier, return nostalgia cue plus Memory Receipt). It also explicitly distinguishes itself from the granular sibling tools, so an agent can identify its role without opening schemas.

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?

It gives a direct when-to-use rule: use this for a complete reconstruction in a single call, and use the granular tools only when driving individual steps. That is an explicit selection rule against the alternative path.

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