Loafy: Sourdough Bread Baking

Change a starter in Loafy

update_starter

DestructiveIdempotent

Change one of the baker's starters, by its id from list_my_starters: only the name, birthday, notes or story given change, and a text given replaces the old text. No starter is deleted. Needs the baker's Loafy account.

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": {
      "id": "<id>"
    },
    "name": "update_starter"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The starter's id, from list_my_starters or add_starter.
`name`	No	The starter's name.
`notes`	No	Notes on the starter, e.g. its flour and how it is fed.
`story`	No	Where the starter comes from, in the baker's words.
`birthday`	No	The day the starter was started, as YYYY-MM-DD.

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.
`saved`	No	What was saved, in one sentence.
`starter`	No	One of the baker's starters.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The starter as saved.",
+  "properties": {
+    "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"
+    },
+    "saved": {
+      "description": "What was saved, in one sentence.",
+      "type": "string"
+    },
+    "starter": {
+      "description": "One of the baker's starters.",
+      "properties": {
+        "age_days": {
+          "description": "Its age in days.",
+          "type": "integer"
+        },
+        "bakes": {
+          "description": "How many bakes it went into.",
+          "type": "integer"
+        },
+        "birthday": {
+          "description": "The day it was started, YYYY-MM-DD.",
+          "type": "string"
+        },
+        "id": {
+          "description": "The starter's id, which update_starter takes.",
+          "type": "string"
+        },
+        "last_baked_on": {
+          "description": "Its last bake, YYYY-MM-DD.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Its name.",
+          "type": "string"
+        },
+        "notes": {
+          "description": "Notes on it.",
+          "type": "string"
+        },
+        "story": {
+          "description": "Its story.",
+          "type": "string"
+        },
+        "url": {
+          "description": "The starter on loafy.ai.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "tool": {
+      "description": "The tool that answered.",
+      "type": "string"
+    },
+    "url": {
+      "description": "The same answer, recipe or entry on loafy.ai.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, idempotent, destructive update, and the description adds useful behavior: only the supplied fields change, provided text replaces old text, no starter is deleted, and a Loafy account is required. The deletion statement clarifies entity preservation but does not fully explain the destructiveHint nuance around overwriting text.

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 one compact sentence, front-loaded with the action and resource. Every clause contributes scope, field behavior, or prerequisite information without waste.

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?

With a low-complexity update tool, a fully described schema, rich annotations, and an output schema, the description covers the remaining agent-relevant details: id source, partial-update semantics, replacement behavior, no deletion, and account requirement.

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 all five parameters are already documented. The description adds meaning beyond the schema by saying the id comes from list_my_starters and that unchanged fields remain untouched, while provided text replaces existing text.

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 names a specific verb and resource: changing a starter, identified by id from list_my_starters. It also scopes exactly which fields can change, so an agent can distinguish it from add_starter and list_my_starters.

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?

It tells the agent where the id comes from (list_my_starters) and states the account prerequisite. It clearly implies use for modifying an existing starter, but it does not explicitly name when to prefer a sibling tool or when not to use this one.

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?