Skip to main content
Glama

Find Sensory Substitutes

find_sensory_substitutes
Read-onlyIdempotent

Find ingredient substitutes when an item is unavailable in a user’s area; returns compound-match scores and a bounded prompt for host-model analysis of gaps.

Instructions

Find ingredient substitutions from the bundled compound dataset and provide a bounded host-model prompt for missing analysis. Returns substitute candidates with compound-match scores and a promptForAgent for the host model. Use when an ingredient is unavailable in the user location. Pass ingredient from the item to substitute and location from the user 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": {
      "ingredient": "<ingredient>",
      "location": "<location>"
    },
    "name": "find_sensory_substitutes"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesUser's location for availability context
ingredientYesThe original ingredient to substitute

Output Schema

NameRequiredDescriptionDefault
modeYes
noteNo
locationYes
ingredientYes
substitutesNo
promptForAgentYes
regionalAvailabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond that by disclosing the source of results (bundled compound dataset), that scoring is compound-match based, and that a 'promptForAgent' fallback is produced for cases the dataset does not cover — meaningful behavior not derivable from annotations.

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?

Four sentences, front-loaded with the action and the return payload before the usage and parameter notes. Nothing is wasted, though the parameter sentence slightly restates schema descriptions and could be trimmed.

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

Completeness5/5

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

Annotations cover safety, an output schema covers return shape, and the description adds the dataset origin, scoring basis, and the promptForAgent fallback path. An agent has everything needed to decide to call it and to interpret the two branches of the result.

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 both parameters are already documented and the baseline is 3. The description adds provenance guidance the schema lacks — take 'ingredient' from the item being substituted and 'location' from the user's area — which helps the agent populate values correctly rather than inventing them.

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 ('Find ingredient substitutions from the bundled compound dataset') and adds the distinctive behavior of returning a bounded host-model prompt. It does not name a sibling such as discover_regional_similars or source_ingredients, so the boundary against those tools is left implicit, which keeps it out of 5 territory.

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 an ingredient is unavailable in the user location' gives a clear triggering condition tied to the two required inputs. There are no explicit exclusions or named alternatives, so an agent cannot tell from this text alone when to prefer a sibling tool.

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