Skip to main content
Glama

Find Scripture for a need, a topic, the words of Jesus, or today

find_scripture_for
Read-onlyIdempotent

Verses for a feeling, a topic, the words of Jesus, or today, read verbatim from the stored text. Modes: need, topic, words_of_jesus, daily_bread. Use when the person names a situation but no reference. Example: {mode:"need", subject:"my mother died"}. Full guide: living-bread://tools/find_scripture_for. Access: no sign-in; shared limit of 300 requests a minute per IP.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_scripture_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFor daily_bread: the calendar day as YYYY-MM-DD in the person's own time zone.
modeNoThe kind of answer. Leave out for a guide to the modes.
limitNoPage size.
detailNolean (default) or full evidence record.
subjectNoThe need, feeling or topic in the person's own words: "I am anxious".
languageNoBCP-47 language code.
translationNoTranslation id (mode translations lists them).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / date / description
      Previous value: -"For daily_bread: the calendar day as YYYY-MM-DD in the person's own time zone. Omit for today (UTC)."New value: +"For daily_bread: the calendar day as YYYY-MM-DD in the person's own time zone."
    • 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: -"The person's BCP-47 language, e.g. \"es\", \"pt-BR\", \"sw\". Picks the best stored public domain or freely licensed Bible for it; translation wins over it."New value: +"BCP-47 language code."
    • changedInput schema / properties / limit / description
      Previous value: -"For need: maximum verses, 1 to 12 (default 5)."New value: +"Page size."
    • changedInput schema / properties / mode / description
      Previous value: -"Which kind of answer: need, topic, words_of_jesus, daily_bread. 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 need, feeling or topic in the person's own words: \"I am anxious\", \"my mother died\", \"shame\", \"forgiveness\". Required for need, topic and words_of_jesus."New value: +"The need, feeling or topic in the person's own words: \"I am anxious\"."
    • changedInput schema / properties / translation / description
      Previous value: -"A stored translation id from read_scripture mode translations, e.g. \"bsb\", \"web\", \"dra\", \"rv1909\", \"cuv\". Default: the King James Version, or the best stored Bible for language."New value: +"Translation id (mode translations lists them)."
    • 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"
      -]
  2. Changed14 schema fields changed
    • 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\"."
  3. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Which kind of answer: need, topic, words_of_jesus, daily_bread. Each mode, and the parameters it needs, is explained in the description."New value: +"Which kind of answer: need, topic, words_of_jesus, daily_bread. 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"
      -]
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that text is returned verbatim from storage (not paraphrased), that no sign-in is required, and that there is a shared 300 requests/minute per-IP rate limit — exactly the operational context annotations cannot convey. It also points to a deeper guide resource for the full contract.

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?

Three dense sentences plus an inline example: purpose, mode enumeration and trigger come first, then the example, then the guide pointer and access constraints. No sentence is redundant and the most important selection cue is front-loaded.

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?

An output schema exists, so return shapes need not be explained, and the description covers modes, access, and rate limits. The one gap is pagination: 'limit' is described only as page size in the schema, and the description never explains how to page through results for a multi-page read.

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 every parameter is already documented in the schema, which sets the baseline at 3. The example {mode:"need", subject:"my mother died"} usefully shows the expected phrasing of subject, but that intent is already stated in the schema, and the description adds nothing about date, translation, or detail semantics.

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 the resource (verses read verbatim from the stored text), enumerates the four retrieval modes, and implicitly separates itself from reference-based siblings by saying to use it 'when the person names a situation but no reference.' An agent can distinguish it from read_scripture or search without opening a schema.

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?

'Use when the person names a situation but no reference' gives a concrete trigger condition, and the mode list plus example shows how to shape the call. It stops short of naming an explicit alternative (e.g., 'if you have a reference, use read_scripture') or stating when not to use it, so it is clear but not fully routing.

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