Skip to main content
Glama
tresor4k

macalc

calculate_bread_hydration

Compute baker's hydration percentage by dividing water weight by flour weight. Input flour and water grams to get hydration percent and dough classification (firm, standard, wet). Ideal for bread recipe analysis.

Instructions

Compute baker's hydration % = water/flour×100. Use for bread recipe analysis. Inputs: flour g, water g. Returns hydration % and dough type (firm/standard/wet). See list_bundles for related 'cuisine' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flour_gramsYesFlour weight grams
water_gramsYesWater weight grams

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool returns hydration % and dough type (firm/standard/wet), and implies a non-destructive calculation. No side effects are mentioned, which is appropriate for a simple calculator.

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?

The description is two sentences, front-loaded with the formula and purpose, and ends with a reference to related tools. Every sentence adds value with no wasted words.

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?

Given the tool's simplicity, the description covers purpose, inputs, formula, output, and a pointer to related tools. This is complete for a calculation tool with an output schema (which the schema coverage confirms but description omits details, but the output description suffices).

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% with descriptions for both parameters. The description adds value by stating the formula and mentioning dough type as output beyond the schema. This enhances understanding beyond the parameter descriptions.

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 computes baker's hydration % with the formula water/flour×100, and specifies its use for bread recipe analysis. It distinguishes itself from the many sibling calculators by providing a precise verb+resource combination.

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?

The description explicitly says 'Use for bread recipe analysis' and references list_bundles for related 'cuisine' calculators, providing context on when to use it. However, it does not mention when not to use it or alternatives, but the context is clear enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server