Skip to main content
Glama
Sign In
Brewers almanack

Brewers almanack

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Suggest Ingredient Substitution

suggest_substitution

Find a substitute brewing ingredient when supplies are short. Compare hops, malt, or yeast alternatives by key properties matched to your beer style and recipe role.

Instructions

Find substitutes for a brewing ingredient (hop, malt, or yeast). Suggests alternatives with similar characteristics, showing key properties for comparison.

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>"
    },
    "name": "suggest_substitution"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoRole in recipe for context (e.g. 'bittering', 'aroma', 'base', 'specialty')
styleNoTarget beer style for context (e.g. 'American IPA', 'Stout')
ingredientYesName of the ingredient to find substitutes for (e.g. 'Citra', 'Maris Otter', 'US-05')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses the tool's basic behavior (finding substitutes, showing properties) but lacks deeper behavioral details such as data sources, number of alternatives, or any limitations. No contradictions with absent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action, no wasted words.

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

Completeness3/5

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

The description covers the basic purpose but lacks detail on output format (e.g., what key properties are shown). With no output schema, more completeness would be beneficial.

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 baseline is 3. The description adds some context (ingredient types) but does not significantly enhance parameter understanding beyond what the schema already provides.

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 clearly states the tool finds substitutes for brewing ingredients (hop, malt, or yeast) and suggests alternatives with similar characteristics, distinguishing it from siblings like search_ingredients or suggest_recipe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies use for substitution needs but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions.

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

Deploy Server

Other Tools