Skip to main content
Glama

Discover Regional Similars

discover_regional_similars
Read-onlyIdempotent

Find bundled dish-family context plus a bounded prompt for similar dishes in neighboring cultures; pass a dish name and cultural region to explore culturally adjacent foods.

Instructions

Find bundled dish-family context and provide a bounded host-model prompt for similar dishes in neighboring cultures. Returns family context with related dishes and a promptForAgent for the host model. Use when exploring culturally adjacent dishes that may share the memory trigger. Pass dishName from the resolved dish and region from its cultural area.

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": {
      "dishName": "<dishName>",
      "region": "<region>"
    },
    "name": "discover_regional_similars"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesThe dish's cultural region
dishNameYesThe dish to find similars for

Output Schema

NameRequiredDescriptionDefault
regionYes
dishNameYes
familyDataNo
knownAliasesYes
cachedResearchNo
promptForAgentYes
resolvedFamilyYes
referenceResearchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description adds real context beyond that: it returns family context with related dishes plus a 'bounded' promptForAgent intended for the host model, and it depends on an already-resolved dish name. It does not clarify what 'bounded' means in practice.

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 action and then the return shape, with no filler. The only waste is mild overlap between 'provide a bounded host-model prompt' and 'a promptForAgent for the host model', which restate the same deliverable.

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 two-parameter read-only tool with an output schema, the description is sufficient: it states the action, the return contents, the usage condition, and the provenance of both arguments. The only residual gap is what 'bounded' constrains in the generated prompt.

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%, so the baseline is 3, but the description adds genuine meaning: dishName must come from the resolved dish, and region must come from its cultural area rather than being an arbitrary string. That qualification is not present in the schema's terse property descriptions.

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?

The description names a specific verb and resource: 'Find bundled dish-family context' and produce a 'promptForAgent for the host model', which is distinct from sibling tools like resolve_dish_name or find_sensory_substitutes. The phrase 'bundled dish-family context' is somewhat jargon-heavy, but the output naming makes the operation concrete.

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?

It gives a clear when-to-use condition ('exploring culturally adjacent dishes that may share the memory trigger') and an implicit prerequisite by instructing the agent to pass a dishName 'from the resolved dish', pointing to a prior resolution step. It stops short of naming an alternative tool or stating when not to use it.

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