The Living Bread

See the Kingdom: believers by city, today, testimonies, worship

see_the_kingdom

Read-onlyIdempotent

The Body of Christ in motion, read only: the map, today's activity, testimonies, worship, sermons, live church services, Living Rooms, songs, games. Example: {mode:"sermons"}. Full guide: living-bread://tools/see_the_kingdom. Access: no sign-in; shared limit of 300 requests a minute per IP.

Input Schema

Name	Required	Description
`mode`	No	The kind of answer. Leave out for a guide to the modes.
`mood`	No	For worship: one word for how they are, e.g. "weary", "thankful".
`word`	No	For testimonies: one word to find in excerpts or journey labels, e.g. "addiction", "grief".
`limit`	No	Page size.
`place`	No	For map. Place name.
`query`	No	For songs: a title or an author, e.g. "grace", "Newton".
`topic`	No	For sermons: one topic word the church tagged, e.g. "hope", "prayer".
`detail`	No	lean (default) or full evidence record.
`language`	No	For worship, songs, videos, sermons. BCP-47 language code.
`local_hour`	No	For worship: the person's local hour, 0 to 23. Defaults to the current UTC hour.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedNov 2, 2026

removedInput schema / $schema

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

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 worship, songs, videos, sermons and outside_testimonies: language as an ISO 639-1 code, e.g. \"es\"."New value: +"For worship, songs, videos, sermons. BCP-47 language code."

changedInput schema / properties / limit / description

Previous value: -"For map (1 to 50, default 12), testimonies (1 to 30, default 8), songs (1 to 24, default 12), videos (1 to 24, default 8), sermons and live_services and living_rooms (1 to 24, default 12) and outside_testimonies (1 to 24, default 8)."New value: +"Page size."

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: map, today, testimonies, worship, map_summary, songs, open_room, videos, games, sermons, live_services, living_rooms, outside_testimonies. 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 / place / description

Previous value: -"For map: a filter matched inside \"city country\", e.g. \"Nairobi\", \"Brazil\". For sermons and live_services: a city the church is in (never an address or coordinates)."New value: +"For map. Place name."

changedInput schema / properties / query / description

Previous value: -"For songs: a title or an author, e.g. \"grace\", \"Newton\". For videos: one topic word, e.g. \"worship\", \"gratitude\". For sermons: a title or speaker. For outside_testimonies: a word in the title or topic."New value: +"For songs: a title or an author, e.g. \"grace\", \"Newton\"."

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"
-]

Changed21 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"
+}

changedInput schema / properties / language / description

Previous value: -"For worship, songs and videos: language as an ISO 639-1 code, e.g. \"es\"."New value: +"For worship, songs, videos, sermons and outside_testimonies: language as an ISO 639-1 code, e.g. \"es\"."

changedInput schema / properties / limit / description

Previous value: -"For map (1 to 50, default 12), testimonies (1 to 30, default 8), songs (1 to 24, default 12) and videos (1 to 24, default 8)."New value: +"For map (1 to 50, default 12), testimonies (1 to 30, default 8), songs (1 to 24, default 12), videos (1 to 24, default 8), sermons and live_services and living_rooms (1 to 24, default 12) and outside_testimonies (1 to 24, default 8)."

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: map, today, testimonies, worship, map_summary, songs, open_room, videos, games. 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: map, today, testimonies, worship, map_summary, songs, open_room, videos, games, sermons, live_services, living_rooms, outside_testimonies. 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: -[
-  "map",
-  "today",
-  "testimonies",
-  "worship",
-  "map_summary",
-  "songs",
-  "open_room",
-  "videos",
-  "games"
-]New value: +[
+  "map",
+  "today",
+  "testimonies",
+  "worship",
+  "map_summary",
+  "songs",
+  "open_room",
+  "videos",
+  "games",
+  "sermons",
+  "live_services",
+  "living_rooms",
+  "outside_testimonies"
+]

changedInput schema / properties / place / description

Previous value: -"For map: a filter matched inside \"city country\", e.g. \"Nairobi\", \"Brazil\"."New value: +"For map: a filter matched inside \"city country\", e.g. \"Nairobi\", \"Brazil\". For sermons and live_services: a city the church is in (never an address or coordinates)."

changedInput schema / properties / query / description

Previous value: -"For songs: a title or an author, e.g. \"grace\", \"Newton\". For videos: one topic word, e.g. \"worship\", \"gratitude\"."New value: +"For songs: a title or an author, e.g. \"grace\", \"Newton\". For videos: one topic word, e.g. \"worship\", \"gratitude\". For sermons: a title or speaker. For outside_testimonies: a word in the title or topic."

addedInput schema / properties / topic

Added value: +{
+  "description": "For sermons: one topic word the church tagged, e.g. \"hope\", \"prayer\".",
+  "maxLength": 40,
+  "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\"."

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: map, today, testimonies, worship, map_summary, songs, open_room, videos, games. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: map, today, testimonies, worship, map_summary, songs, open_room, videos, games. 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"
-]
```

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / language / description

Previous value: -"For worship: preferred song language as an ISO 639-1 code, e.g. \"es\"."New value: +"For worship, songs and videos: language as an ISO 639-1 code, e.g. \"es\"."

changedInput schema / properties / limit / description

Previous value: -"For map (1 to 50, default 12) and testimonies (1 to 30, default 8)."New value: +"For map (1 to 50, default 12), testimonies (1 to 30, default 8), songs (1 to 24, default 12) and videos (1 to 24, default 8)."

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: map, today, testimonies, worship, map_summary. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: map, today, testimonies, worship, map_summary, songs, open_room, videos, games. Each mode, and the parameters it needs, is explained in the description."

changedInput schema / properties / mode / enum

Previous value: -[
-  "map",
-  "today",
-  "testimonies",
-  "worship",
-  "map_summary"
-]New value: +[
+  "map",
+  "today",
+  "testimonies",
+  "worship",
+  "map_summary",
+  "songs",
+  "open_room",
+  "videos",
+  "games"
+]

addedInput schema / properties / query

Added value: +{
+  "description": "For songs: a title or an author, e.g. \"grace\", \"Newton\". For videos: one topic word, e.g. \"worship\", \"gratitude\".",
+  "maxLength": 80,
+  "type": "string"
+}

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / mode / description

Previous value: -"Which kind of answer: map, today, testimonies, worship. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: map, today, testimonies, worship, map_summary. Each mode, and the parameters it needs, is explained in the description."

changedInput schema / properties / mode / enum

Previous value: -[
-  "map",
-  "today",
-  "testimonies",
-  "worship"
-]New value: +[
+  "map",
+  "today",
+  "testimonies",
+  "worship",
+  "map_summary"
+]

AddedOct 6, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context: no sign-in required and a shared rate limit of 300 requests/minute per IP — exactly the kind of constraint an agent needs before planning a burst of calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact at roughly 45 words with no wasted sentences, but it is not front-loaded: the vague theological framing precedes the actual content list, and the mode enumeration partially duplicates the enum already in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 13-mode, 10-parameter tool: an output schema exists so return values needn't be described, and per-parameter mode bindings live in the schema. What is missing is sibling differentiation against find_churches/find_gatherings and any hint of how to choose among the 13 modes without consulting the external guide.

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 each of the 10 parameters already carries its own mode-binding explanation (e.g. mood "For worship", word "For testimonies"). The description only adds a single example, {mode:"sermons"}, which is marginal value over the schema baseline of 3.

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

Purpose3/5

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

The opening phrase "The Body of Christ in motion, read only" is atmospheric rather than operational — there is no verb like retrieve/browse. The subsequent list (map, today's activity, testimonies, worship, sermons, live services, Living Rooms, songs, games) does convey the content domains, but it overlaps heavily with siblings find_churches, find_gatherings, and find_communities without distinguishing itself.

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

Usage Guidelines2/5

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

No statement of when to use this versus the many sibling find_* tools, despite obvious overlap on churches, gatherings, and communities. The only routing help is the pointer to living-bread://tools/see_the_kingdom, which defers the decision to an external document the agent may not fetch.

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?