The Living Bread

Learn the faith from the house's own pages

learn_the_faith

Read-onlyIdempotent

The house's own pages on the faith: the gospel, beliefs, parables, miracles, hymns, a prayer for a situation, a hard season, saints, the church year, the meaning of a name, other faiths. Pick a mode. Example: {mode:"a_prayer_for", subject:"a friend who is sick"}. Full guide: living-bread://tools/learn_the_faith. Access: no sign-in; shared limit of 300 requests a minute per IP.

Input Schema

Name	Required	Description
`date`	No	For saint_of_the_day: "October 4", "4 Oct" or YYYY-MM-DD; the year is ignored.
`kind`	No	For heritage: which kind of entity subject names.
`mode`	No	The kind of answer. Leave out for a guide to the modes.
`year`	No	For church_year: the year, 1900 to 2099; read from subject when omitted, default the next one ahead.
`detail`	No	lean (default) or full evidence record.
`subject`	No	The one thing asked about, in plain words: a doctrine, parable, miracle, hymn.
`language`	No	For explore_gospel. BCP-47 language code.
`compare_with`	No	For compare_traditions: the second denomination, e.g. "Eastern Orthodox Church".

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedNov 2, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / date / description

Previous value: -"For saint_of_the_day: \"October 4\", \"4 Oct\" or YYYY-MM-DD; the year is ignored. Omit for today (UTC)."New value: +"For saint_of_the_day: \"October 4\", \"4 Oct\" or YYYY-MM-DD; the year is ignored."

changedInput schema / properties / detail / description

Previous value: -"lean (default): the answer, its credit and one door. full: the complete evidence record (per-passage hashes, canon, layers)."New value: +"lean (default) or full evidence record."

changedInput schema / properties / language / description

Previous value: -"For explore_gospel: en, es, pt or fr; the Scripture is read from a stored Bible in that language when one is held."New value: +"For explore_gospel. BCP-47 language code."

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel, church_year, page. Each mode, and the parameters it needs, is explained in the description. Leave it out and the answer says what each mode is for."New value: +"The kind of answer. Leave out for a guide to the modes."

changedInput schema / properties / subject / description

Previous value: -"The one thing asked about, in plain words: a doctrine, parable, miracle, hymn, name, saint, denomination, background, life moment or situation. Required for every mode except gospel and saint_of_the_day."New value: +"The one thing asked about, in plain words: a doctrine, parable, miracle, hymn."

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / properties / answered_by

Removed value: -{
-  "description": "The implementation that answered (the same tool name the signed-in endpoint lists).",
-  "type": "string"
-}

removedOutput schema / properties / attribution

Removed value: -{
-  "description": "Credit: The Living Bread (living-bread.org).",
-  "type": "string"
-}

removedOutput schema / properties / content_flags

Removed value: -{
-  "description": "Set when retrieved text was withheld.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / content_layers

Removed value: -{
-  "additionalProperties": {},
-  "description": "full detail: Scripture versus interpretation versus reflection.",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / evidence

Removed value: -{
-  "additionalProperties": {},
-  "description": "When Scripture was read: translation, license, attribution, corpus version (full detail adds hashes and canon).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / freshness

Removed value: -{
-  "additionalProperties": {},
-  "description": "kind, retrieved_at, available_now (true only when verified live).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / ids

Removed value: -{
-  "description": "Up to 25 ids in this answer.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / ignored_params

Removed value: -{
-  "description": "Parameters given that this mode does not use.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / license

Removed value: -{
-  "description": "License URL (CC BY 4.0 unless stated).",
-  "type": "string"
-}

removedOutput schema / properties / mode

Removed value: -{
-  "description": "The mode that answered.",
-  "type": "string"
-}

removedOutput schema / properties / next_actions

Removed value: -{
-  "description": "Links to open next.",
-  "items": {
-    "additionalProperties": {},
-    "properties": {
-      "label": {
-        "type": "string"
-      },
-      "url": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "label",
-      "url"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / ok

Removed value: -{
-  "description": "Always true on success.",
-  "type": "boolean"
-}

removedOutput schema / properties / result_state

Removed value: -{
-  "description": "\"empty\" when nothing matched.",
-  "enum": [
-    "useful",
-    "empty"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / scripture_fields

Removed value: -{
-  "description": "Which fields are Scripture (all else is the house's own words).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / source_url

Removed value: -{
-  "description": "A public page of The Living Bread this answer came from.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / visibility

Removed value: -{
-  "description": "\"public\" or \"yours\".",
-  "type": "string"
-}

removedOutput schema / required

Removed value: -[
-  "mode",
-  "answered_by"
-]

Changed14 schema fields changedNov 2, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "lean (default): the answer, its credit and one door. full: the complete evidence record (per-passage hashes, canon, layers).",
+  "enum": [
+    "lean",
+    "full"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / attribution / description

Previous value: -"Credit line for the data: The Living Bread (living-bread.org)."New value: +"Credit: The Living Bread (living-bread.org)."

changedOutput schema / properties / content_flags / description

Previous value: -"[\"instruction_like_text_removed\"] when retrieved text was withheld."New value: +"Set when retrieved text was withheld."

changedOutput schema / properties / content_layers / description

Previous value: -"Which fields are Scripture and which are human interpretation or reflection."New value: +"full detail: Scripture versus interpretation versus reflection."

changedOutput schema / properties / evidence / description

Previous value: -"Present when Scripture was read: translation, canon, corpus version, attribution, and a SHA-256 per passage."New value: +"When Scripture was read: translation, license, attribution, corpus version (full detail adds hashes and canon)."

changedOutput schema / properties / freshness / description

Previous value: -"How current the answer is: kind (scheduled | recently_observed | verified_live | record), retrieved_at, available_now (true only when activity was verified live)."New value: +"kind, retrieved_at, available_now (true only when verified live)."

changedOutput schema / properties / ids / description

Previous value: -"Up to 25 ids found in this answer, for follow-up calls."New value: +"Up to 25 ids in this answer."

changedOutput schema / properties / license / description

Previous value: -"License URL of the returned data (CC BY 4.0 unless stated)."New value: +"License URL (CC BY 4.0 unless stated)."

changedOutput schema / properties / next_actions / description

Previous value: -"Up to 4 links the person can open next."New value: +"Links to open next."

changedOutput schema / properties / ok / description

Previous value: -"Always true on a successful answer (errors come back as isError, never here)."New value: +"Always true on success."

changedOutput schema / properties / result_state / description

Previous value: -"\"empty\" when nothing matched (count 0, no results); the text then says so plainly."New value: +"\"empty\" when nothing matched."

addedOutput schema / properties / scripture_fields

Added value: +{
+  "description": "Which fields are Scripture (all else is the house's own words).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / source_url / description

Previous value: -"The first public web page this answer came from or points to."New value: +"A public page of The Living Bread this answer came from."

changedOutput schema / properties / visibility / description

Previous value: -"\"public\" for shared data, \"yours\" for the signed-in believer's own data."New value: +"\"public\" or \"yours\"."

Changed3 schema fields changedOct 30, 2026

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel. Each mode, and the parameters it needs, is explained in the description. Leave it out and the answer says what each mode is for."New value: +"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel, church_year, page. Each mode, and the parameters it needs, is explained in the description. Leave it out and the answer says what each mode is for."

changedInput schema / properties / mode / enum

Previous value: -[
-  "gospel",
-  "belief",
-  "parable",
-  "miracle",
-  "hymn",
-  "name_meaning",
-  "saint",
-  "saint_of_the_day",
-  "heritage",
-  "compare_traditions",
-  "other_faiths",
-  "hard_season",
-  "a_prayer_for",
-  "explore_gospel"
-]New value: +[
+  "gospel",
+  "belief",
+  "parable",
+  "miracle",
+  "hymn",
+  "name_meaning",
+  "saint",
+  "saint_of_the_day",
+  "heritage",
+  "compare_traditions",
+  "other_faiths",
+  "hard_season",
+  "a_prayer_for",
+  "explore_gospel",
+  "church_year",
+  "page"
+]

addedInput schema / properties / year

Added value: +{
+  "description": "For church_year: the year, 1900 to 2099; read from subject when omitted, default the next one ahead.",
+  "maximum": 2099,
+  "minimum": 1900,
+  "type": "integer"
+}

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel. Each mode, and the parameters it needs, is explained in the description. Leave it out and the answer says what each mode is for."

removedInput schema / required
```
Removed value: -[
-  "mode"
-]
```

Changed3 schema fields changedOct 18, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "For explore_gospel: en, es, pt or fr; the Scripture is read from a stored Bible in that language when one is held.",
+  "enum": [
+    "en",
+    "es",
+    "pt",
+    "fr"
+  ],
+  "type": "string"
+}

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a_prayer_for, explore_gospel. Each mode, and the parameters it needs, is explained in the description."

changedInput schema / properties / mode / enum

Previous value: -[
-  "gospel",
-  "belief",
-  "parable",
-  "miracle",
-  "hymn",
-  "name_meaning",
-  "saint",
-  "saint_of_the_day",
-  "heritage",
-  "compare_traditions",
-  "other_faiths",
-  "hard_season",
-  "a_prayer_for"
-]New value: +[
+  "gospel",
+  "belief",
+  "parable",
+  "miracle",
+  "hymn",
+  "name_meaning",
+  "saint",
+  "saint_of_the_day",
+  "heritage",
+  "compare_traditions",
+  "other_faiths",
+  "hard_season",
+  "a_prayer_for",
+  "explore_gospel"
+]

AddedOct 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful operational context beyond annotations: no sign-in is required and there is a shared rate limit of 300 requests per minute per IP.

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 reasonably compact and front-loads the content scope before giving mode guidance, an example, a guide URI, and access constraints. The long topic list is dense but still earns its place by showing the breadth of modes.

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?

Given the output schema and rich annotations, the description covers the key missing context: mode selection, an example invocation, a full guide reference, and access/rate-limit details. It is only incomplete in not routing the agent away from sibling tools when those are more appropriate.

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%, so the schema already documents all eight parameters in detail. The description adds a helpful mode+subject example, but it does not meaningfully expand parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a multi-mode faith-content resource and lists the kinds of pages it covers, so an agent can tell it retrieves teaching material rather than scripture or community data. It does not explicitly distinguish itself from siblings such as read_scripture, find_scripture_for, or start_with_christ.

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

Usage Guidelines3/5

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

It says to "Pick a mode" and gives one concrete example, which implies usage. However, it does not state when to use this tool instead of sibling tools like read_scripture, find_scripture_for, or start_with_christ, nor does it give exclusions.

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

All The Living Bread 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?