Skip to main content
Glama

Collect Food Memory

collect_food_memory
Read-onlyIdempotent

Structures a raw nostalgic food or drink memory into clues, missing information, and optional follow-up questions with a sufficiency score.

Instructions

Structure a raw food-or-drink memory fragment into clues, missing information, and optional follow-up questions. Returns a structured memory object with a sufficiency score; when region, sensory details, and context are present, no follow-up questions are needed. Use when a user first describes a nostalgic food or drink memory. Pass memoryText from the user raw memory.

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": {
      "memoryText": "<memoryText>"
    },
    "name": "collect_food_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoryTextYesRaw user memory, spelling fragment, family story, or sensory clue
knownRegionNoOptional known country, island, region, or community
userLocationNoOptional current location for later adaptation
knownLanguageNoOptional known language or dialect context

Output Schema

NameRequiredDescriptionDefault
rawMemoryYes
reassuranceYes
userLocationNo
nextQuestionsYes
extractedCluesYes
inferredContextYes
normalizedMemoryYes
extractionMetadataNo
missingInformationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context the annotations cannot: the sufficiency score and the conditional rule that follow-up questions are omitted when region, sensory details, and context are present.

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?

Three sentences, front-loaded with the transformation and followed by output behavior and the usage trigger; nothing is padding. The sufficiency-score sentence is slightly dense but each clause carries information an agent needs.

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?

With an output schema present, the description need not enumerate return fields, and annotations cover safety, so the remaining job is intent and sequencing, which it mostly does. The gap is the handoff: it never says where the structured memory or follow-up questions go next (e.g., toward reconstruct_food_memory), which matters in a large sibling set.

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 every parameter is already documented, which sets the baseline at 3. The description adds only a light constraint on memoryText ('from the user raw memory'), and says nothing about the three optional parameters (knownRegion, userLocation, knownLanguage) beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Structure a raw food-or-drink memory fragment into clues, missing information, and optional follow-up questions') and describes the returned object. It also scopes the entry point ('Use when a user first describes a nostalgic food or drink memory'), which implicitly separates it from downstream siblings like reconstruct_food_memory, but no sibling is named explicitly.

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?

Gives a clear triggering condition: use when a user first describes a nostalgic food or drink memory, plus an input instruction to pass memoryText from the raw user memory. No explicit exclusions or named alternatives, so it stops short of full routing guidance.

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