Skip to main content
Glama
Sign In
Brewers almanack

Brewers almanack

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Diagnose Off-Flavour

diagnose_off_flavour

Identify the cause of a beer off-flavour from taste or aroma descriptions, then get the compound, prevention steps, detection threshold, and acceptable styles.

Instructions

Diagnose beer off-flavours from taste or aroma descriptions. Returns the likely compound, causes, prevention steps, detection threshold, and styles where it may be acceptable.

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": {
      "description": "<description>"
    },
    "name": "diagnose_off_flavour"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesTaste or aroma description of the off-flavour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It explicitly lists what is returned (likely compound, causes, prevention, threshold, acceptable styles), providing good transparency about behavior and output.

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: one for action, one for output. No wasted words; every sentence is informative and direct.

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 single-parameter tool with no output schema, the description is adequately complete—covers purpose, input, and output. Missing any limitations or error handling, but not critical for this context.

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 description coverage is 100%, so the parameter is well-defined. The description adds value by explaining the output context, linking the input to specific return fields.

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 verb 'Diagnose' combined with 'beer off-flavours' is specific and clear. The tool's purpose is distinct from sibling tools like match_water_profile, pairing_guide, etc., which focus on different aspects of brewing.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage from taste/aroma descriptions but doesn't exclude vague inputs or offer alternatives.

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