Skip to main content
Glama
cacack

mcp-server-brewfather

by cacack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_batch

Change a batch's status or record measured gravities, volumes, and temperatures in BrewFather to keep brew records accurate.

Instructions

Update a batch's status and/or measured values.

``status``: Planning, Brewing, Fermenting, Conditioning, Completed, Archived.
``measurements`` keys (metric only — gravities SG, volumes liters, temps °C):
measuredMashPh, measuredBoilSize, measuredFirstWortGravity,
measuredPreBoilGravity, measuredPostBoilGravity, measuredKettleSize,
measuredOg, measuredFermenterTopUp, measuredBatchSize, measuredFg,
measuredBottlingSize, carbonationTemp. Returns {batch_id, result}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
batch_idYes
measurementsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "update_batchDictOutput",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses allowed status values, measurement units, and return shape, but says nothing about permissions, side effects, reversibility, validation failures, or whether omitted fields are left unchanged.

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?

The purpose is front-loaded, and the detailed enum and measurement lists are necessary because the schema lacks descriptions. It is slightly padded by the return-shape note, which is redundant given the output schema, but otherwise efficient.

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 supplies enough detail to construct a valid call, especially for status and measurements. However, for a mutation tool with no annotations, it omits usage context and behavioral consequences; the return mention is unnecessary because an output schema exists.

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 0%, so the description must compensate. It does this well for two of three parameters by listing all valid status values and all measurement keys with metric units. batch_id is not described, keeping it from a 5.

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 first sentence states a specific verb and resource: 'Update a batch's status and/or measured values.' It makes the mutation scope clear and, together with the tool name, distinguishes this from sibling read tools like get_batch and find_batches.

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

Usage Guidelines2/5

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

The description gives no when-to-use context, no prerequisites, and no alternatives. An agent can infer that this updates an existing batch, but nothing states when to choose this over sibling tools or what conditions must be met first.

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