Skip to main content
Glama
Sign In
Brewers almanack

Brewers almanack

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Suggest Recipe

suggest_recipe

Find a complete beer recipe for any target style, with grain bill, hop schedule, yeast selection, and process parameters.

Instructions

Suggest a beer recipe for a target style. Returns grain bill, hop schedule, yeast selection, and process parameters.

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": {
      "style": "<style>"
    },
    "name": "suggest_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesTarget beer style for the recipe
batch_size_litresNoBatch size in litres

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool 'suggests' (non-mutating) and lists outputs, but lacks details on prerequisites, side effects, or deterministic behavior. Adequate but not exceptional.

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?

Single sentence, front-loaded with purpose, no redundant words. Efficiently communicates the tool's function and outputs.

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 simple tool with 2 parameters and no output schema, the description covers the returned components well. It could mention the default for batch_size_litres, but overall sufficient.

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 coverage is 100% with both parameters described. The description does not add additional meaning beyond the schema; it merely restates 'target style' and 'batch size.' Baseline 3 is appropriate.

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's action: 'Suggest a beer recipe for a target style.' It specifies the outputs (grain bill, hop schedule, etc.) and distinguishes it from sibling tools like 'search_styles' or 'search_ingredients' which serve different purposes.

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 usage (when you want a recipe suggestion) but does not explicitly state when not to use it or provide alternative tools. Given siblings are distinct, an agent may infer correctly, but no explicit guidance is given.

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