Skip to main content
Glama

Plan Dish Research

plan_dish_research
Read-onlyIdempotent

Generates a research plan from food or drink memory clues, with named hypotheses, targeted search queries, source preferences, and facts to verify for identifying a remembered dish.

Instructions

Turn collected food or drink memory clues into hypotheses, search queries, source preferences, and facts to verify. Returns a research plan with named hypotheses and targeted queries. Use when preparing research directions after collecting a memory. Pass memory from collect_food_memory output.

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": "plan_dish_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoryYesStructured output from collect_food_memory

Output Schema

NameRequiredDescriptionDefault
hypothesesYes
factsToVerifyYes
searchQueriesYes
researchedFactsNoSource-backed facts from web search about this dish
questionsForUserYes
researchRequiredYes
preferredSourceTypesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds only pipeline position and the shape of the result ('named hypotheses and targeted queries'), which overlaps with the existing output schema. Nothing is said about determinism, cost, or limits on how many hypotheses/queries are produced.

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 short sentences, front-loaded with the core verb and resource, followed by output and usage. The return-value sentence is partly redundant given an output schema exists, but nothing else is padded.

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 rich annotations, a single fully documented nested parameter, and an output schema, the description needs only purpose and placement — both are supplied. The remaining gap is how this planning step differs from adjacent planning/analysis siblings, which is left implicit.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the semantics and the baseline of 3 applies. The description's contribution ('Pass memory from collect_food_memory output') confirms the producer of that object but adds no new detail about which nested fields are actually consumed.

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 transformation ('turn collected food or drink memory clues into hypotheses, search queries, source preferences, and facts to verify') and states the artifact produced ('a research plan with named hypotheses and targeted queries'). It also identifies the upstream sibling collect_food_memory, so an agent can place it in the pipeline 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 Guidelines4/5

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

'Use when preparing research directions after collecting a memory' gives a clear trigger and ordering constraint, and 'Pass memory from collect_food_memory output' names the exact input source. It stops short of naming alternatives or when-not conditions (e.g., versus plan_tool_workflow or analyze_nostalgic_dish), which keeps it below a 5.

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