Loafy: Sourdough Bread Baking

Pizza dough calculator

calculate_pizza_dough

Read-onlyIdempotent

Calculate pizza dough in grams from the number of pizzas, the ball weight and hydration, with either fresh yeast or sourdough starter. Returns flour, water, salt, leavening and toppings, plus a link to the same recipe on loafy.ai. method_url is the step-by-step method to hand the baker. A loaf of bread is calculate_bread_dough. A value outside its range is corrected, and notes name it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_pizza_dough"
  }
}

Input Schema

Name	Required	Description	Default
`oven`	No	home is a domestic oven, pizza an Ooni or Roccbox, wood a wood-fired oven.	home
`pizzas`	No	How many pizzas.
`dough_type`	No	Leavened with fresh yeast or with sourdough starter.	yeast
`hydration_percent`	No	Water as a percentage of flour. 55-65 is easy to handle, above 70 is expert.
`weight_per_pizza_g`	No	Dough ball weight in grams. Left out, it follows the oven: 250 g home, 270 g pizza oven, 280 g wood-fired.

Output Schema

Name	Required	Description
`url`	No	The same answer, recipe or entry on loafy.ai.
`note`	No	A remark on the whole result, such as why nothing was found.
`tool`	No	The tool that answered.
`input`	No	The arguments as the tool used them, after any correction.
`notes`	No	What was corrected or left out, such as a value outside its range.
`toppings`	No	Toppings for all the pizzas: grams, and basil as leaves and pots.
`method_url`	No	The complete Neapolitan pizza method, step by step, sourdough included, on The Bread Code's pizza calculator.
`ingredients`	No	Flour, water, salt and the leavening (fresh yeast or starter), in grams.
`total_dough_g`	No	All the dough, in grams.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedOutput schema / properties / method_url

Added value: +{
+  "description": "The complete Neapolitan pizza method, step by step, sourdough included, on The Bread Code's pizza calculator.",
+  "type": "string"
+}

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Pizza dough in grams.",
+  "properties": {
+    "ingredients": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "description": "Flour, water, salt and the leavening (fresh yeast or starter), in grams.",
+      "type": "object"
+    },
+    "input": {
+      "description": "The arguments as the tool used them, after any correction.",
+      "properties": {},
+      "type": "object"
+    },
+    "note": {
+      "description": "A remark on the whole result, such as why nothing was found.",
+      "type": "string"
+    },
+    "notes": {
+      "description": "What was corrected or left out, such as a value outside its range.",
+      "items": {
+        "description": "A correction or remark.",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "description": "The tool that answered.",
+      "type": "string"
+    },
+    "toppings": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "description": "Toppings for all the pizzas: grams, and basil as leaves and pots.",
+      "type": "object"
+    },
+    "total_dough_g": {
+      "description": "All the dough, in grams.",
+      "type": "number"
+    },
+    "url": {
+      "description": "The same answer, recipe or entry on loafy.ai.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: out-of-range inputs are silently corrected and the corrections are surfaced in the notes field. It also discloses the return payload (flour, water, salt, leavening, toppings, shareable link, method_url). Minor gap: no statement on whether the returned quantities are exact or rounded.

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?

Four short sentences, front-loaded with the calculation and followed by output, sibling disambiguation, and edge-case handling in descending priority. Slightly clipped phrasing ("A value outside its range is corrected") costs a little clarity but no sentence is filler.

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?

An output schema exists, so return values did not need spelling out, yet the description still names the key outputs and the purpose of method_url. Combined with the clamping disclosure and the bread-calculator disambiguation, an agent has enough to invoke this correctly; only rounding precision and default-resolution details are absent.

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%, so baseline is 3, and the description earns an extra point by explaining the clamping-and-notes behavior that governs every numeric parameter. It also restates the key input dimensions and the yeast/sourdough choice in prose, reinforcing what the enum fields mean.

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?

Opens with a specific verb+resource ("Calculate pizza dough in grams") and names the exact inputs that drive the calculation (number of pizzas, ball weight, hydration, yeast vs sourdough). It explicitly distinguishes itself from the nearest sibling by stating "A loaf of bread is calculate_bread_dough."

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 routes the agent away from the bread calculator and makes the pizza-dough scope unambiguous. It does not address other plausible siblings such as estimate_bulk_fermentation or plan_sourdough_bake, and gives no explicit exclusion of when not to use it, so it stops short of a 5.

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

All Loafy: Sourdough Bread Baking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?