Skip to main content
Glama

Loafy: Sourdough Bread Baking

Search The Sourdough Framework

search_sourdough_book
Read-onlyIdempotent

Search Hendrik Kleinwächter's open-source book The Sourdough Framework and get the passages that answer a question, each with its chapter, a link and the part of the book it comes from, which read_sourdough_book returns in full. The book covers starters, fermentation, flour, hydration, shaping, baking and troubleshooting. It is written in English, and the search matches English words. Hendrik's published answers to common questions are find_sourdough_answer, and a whole chapter is read_sourdough_book. Without a Loafy account, reading and searching the book and the answers is limited to 3 questions a day, every lookup within 15 minutes counting as one question; with an account it has no limit. The calculators, the guides and the book's table of contents need no 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": {
      "query": "<query>"
    },
    "name": "search_sourdough_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many passages to return. Defaults to 3.
queryYesWhat to look up, in English, e.g. "starter smells like acetone" or "bulk fermentation temperature".

Output Schema

NameRequiredDescriptionDefault
urlNoThe same answer, recipe or entry on loafy.ai.
noteNoA remark on the whole result, such as why nothing was found.
toolNoThe tool that answered.
inputNoThe arguments as the tool used them, after any correction.
notesNoWhat was corrected or left out, such as a value outside its range.
licenseNoThe licence of the book's text: CC BY-SA 4.0, with attribution.
passagesNoThe passages that answer the question.
suggestionNoWhere to look next when nothing fits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Passages from The Sourdough Framework.",
      +  "properties": {
      +    "input": {
      +      "description": "The arguments as the tool used them, after any correction.",
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "license": {
      +      "description": "The licence of the book's text: CC BY-SA 4.0, with attribution.",
      +      "type": "string"
      +    },
      +    "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"
      +    },
      +    "passages": {
      +      "description": "The passages that answer the question.",
      +      "items": {
      +        "properties": {
      +          "chapter": {
      +            "description": "The chapter.",
      +            "type": "string"
      +          },
      +          "part": {
      +            "description": "Its number and title, which read_sourdough_book takes.",
      +            "type": "string"
      +          },
      +          "section": {
      +            "description": "The section within it.",
      +            "type": "string"
      +          },
      +          "text": {
      +            "description": "The passage.",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "The chapter on the book's website.",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "suggestion": {
      +      "description": "Where to look next when nothing fits.",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "The tool that answered.",
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "The same answer, recipe or entry on loafy.ai.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: per-day question quotas, the account/no-account distinction, and which resources are free. This is the rare case where the prose meaningfully extends the safety profile.

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 description is dense but front-loaded with the core purpose before the alternatives and quota caveats. Almost every sentence earns its place, though the quota details could be tightened slightly.

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 an output schema present, return values need not be documented yet are described anyway. Alternatives, language constraints, and access limits are all covered, leaving nothing material an agent needs missing.

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 the baseline is 3, but the description adds the constraint that the book and matching are English-only, which informs how the query parameter should be phrased. The limit parameter is left to the schema, so it does not reach a full 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?

States a specific verb (search) and resource (The Sourdough Framework book) and describes the return shape (passages with chapter, link, source part). It explicitly distinguishes itself from read_sourdough_book (returns full chapter) and find_sourdough_answer (published answers), so an agent can select it without opening another schema.

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

Usage Guidelines5/5

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

Provides explicit routing: use read_sourdough_book for full chapters and find_sourdough_answer for published answers. It also states when access is limited (3 questions/day without a Loafy account, 15-minute window counting as one question) and what needs no account, which is exactly the operational context an agent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources