Skip to main content
Glama

Loafy: Sourdough Bread Baking

Read The Sourdough Framework

read_sourdough_book
Read-onlyIdempotent

Read a chapter or section of Hendrik Kleinwächter's open-source book The Sourdough Framework in full, by its number from get_sourdough_book_contents or by its title. Returns the text with its chapter, link and licence; a chapter longer than about 40,000 characters comes in pages. 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": {
      "part": "<part>"
    },
    "name": "read_sourdough_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of a long chapter. Most parts have one.
partYesA chapter or section: its number from get_sourdough_book_contents, e.g. "8" or "8.3", or its title, e.g. "Bulk fermentation".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations covering the safety profile, the description adds substantial context: the return payload (chapter text with link and licence), the ~40,000-character pagination rule, and detailed rate limits (3 questions/day unauthenticated, 15-minute coalescing window, unlimited with an account, exempt calculators/guides/TOC). This is exactly what an agent needs to avoid surprise throttling.

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?

Front-loads the core action and return behavior, then adds operational constraints. Mostly every sentence earns its place, though the account/limit clause is dense enough to be slightly effortful in one breath.

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 no output schema, the description still explains what comes back, how long chapters paginate, and the auth/rate-limit environment. Nothing material for a correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and already documents both 'part' (number or title) and 'page'. The description restates the same semantics without adding syntax or edge-case detail beyond what the schema provides, so baseline 3 applies.

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 (read) and resource (a chapter/section of a named book), plus the scope 'in full'. It clearly separates itself from search_sourdough_book and get_sourdough_book_contents by naming the latter as the source of valid part numbers.

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?

Tells the agent to obtain the part identifier from get_sourdough_book_contents and implies reading versus searching (mentioning search limits alongside). It gives clear context for when to use this tool but never explicitly names search_sourdough_book as the alternative for lookup-style access.

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