Skip to main content
Glama

Resolve Dish Name

resolve_dish_name
Read-onlyIdempotent

Resolve an uncertain, misspelled, or transliterated dish name to its canonical name, family, aliases, and broad region using fuzzy matching and bundled transliteration data.

Instructions

Resolve a dish name to its canonical family, aliases, transliterations, and broad region using fuzzy matching and bundled transliteration data. Returns a resolution object with the canonical name, family, and matched aliases. Use when the user dish name is uncertain, misspelled, or transliterated. Pass input from the dish name as the user described it.

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": {
      "input": "<input>"
    },
    "name": "resolve_dish_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe dish name as the user described it, including spelling variants or transliterations
memoryNoOptional structured memory context from collect_food_memory
researchedFactsNoOptional source-backed facts already gathered for this unresolved name

Output Schema

NameRequiredDescriptionDefault
inputYes
scoreNo
regionYes
aliasesYes
matchTypeNo
candidatesNo
confidenceYes
dishFamilyYes
canonicalNameYes
transliterationsYes
needsClarificationNo
clarificationPromptNo

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 declare readOnly, idempotent, closed-world and non-destructive, so safety is covered; the description adds genuinely new behavior by disclosing the fuzzy-matching approach, the bundled transliteration corpus, and the shape of the resolution object (canonical name, family, matched aliases). It does not say what happens on a miss or whether matches carry confidence, but that gap is partly absorbed by the existing output schema.

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 front-loaded sentences move cleanly from what it does, to what it returns, to when to use it and what to pass. The closing sentence is nearly a verbatim echo of the `input` schema description, which is the one redundant element worth cutting.

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 annotations covering safety, an output schema covering return values, and a fully described input schema, the description needs only to explain the operation and the trigger, and it does both. The remaining omission is whether the optional memory/researchedFacts inputs materially improve resolution, which a caller of a nested-schema tool would want to know.

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 all three parameters, including the large nested memory object and researchedFacts, are already documented in the schema. The description's only parameter guidance restates the schema's own wording for `input` and says nothing about when to supply memory or researchedFacts, so it adds essentially no meaning beyond the structured fields. Baseline 3 applies.

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 (resolve) and resource (dish name) plus the concrete outputs: canonical family, aliases, transliterations, broad region, and the mechanism (fuzzy matching with bundled transliteration data). It does not name a sibling it replaces or is replaced by, so the agent must infer routing from names alone, but the operation itself is unambiguous.

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 the user dish name is uncertain, misspelled, or transliterated" gives a clear triggering condition, and the last sentence tells the caller what to feed in. There is no explicit when-not or named alternative (e.g., when a name is already canonical, or when to reach for discover_regional_similars instead), so routing is only partly pinned down.

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