ALWAYS USE THIS when discussing any Greek or Hebrew word, theological term, or concept.

Even if you know the word from training, this tool provides verified lexical data.

IMPORTANT: When presenting word studies, ALWAYS SHOW:

• The word in original script: ἀγάπη or אֱלֹהִים

• Transliteration: agapē, elohim

• Strong's number: G26, H430

• Full definition and semantic range

• Key passages showing usage

Format example in your response: ἀγάπη (agapē, G26) Definition: "Love, goodwill, benevolence; the love of God for humanity" Usage: Occurs 116 times in the NT Key passages: John 3:16, 1 Corinthians 13, 1 John 4:8

This makes responses scholarly and shows the depth available through original languages.

ALWAYS USE THIS when any Bible verse is mentioned or relevant.

Even if you can quote a verse from memory, this tool provides:

• The actual verse text (not paraphrased from training)

• Original Greek/Hebrew text (ALWAYS DISPLAY THIS in your response)

• Word-by-word breakdown with Strong's numbers

• Genre-specific interpretation guidance

IMPORTANT: When you use this tool, SHOW the original language text in your response. This is what makes the Study Bible valuable - users see the actual Greek/Hebrew.

Format example in your response: Romans 13:1: "Let every soul be subject to the governing authorities..." Greek: Πᾶσα ψυχὴ ἐξουσίαις ὑπερεχούσαις ὑποτασσέσθω... Key term: ἐξουσία (exousia, G1849) - "authority, power"

Supports: 'John 3:16', 'Gen 1:1', 'Romans 3:21-26', etc.

USE THIS to find Greek/Hebrew words for English concepts.

When a user asks about a biblical concept (love, faith, salvation, sin, grace, etc.), search for the original language words to provide accurate, grounded information.

This finds multiple words that translate a concept (e.g., "love" → agape, phileo, eros) so you can explain the distinctions and nuances.

Also use when you want to identify the Greek/Hebrew behind an English term.

USE THIS whenever you are explaining, exegeting, or arguing from a specific Bible verse — and for any theological or doctrinal question.

Two complementary modes:

By verse reference (most common). Pass reference="John 3:16" (or any canonical verse) to get the passages historically read alongside it. The database draws from four scholarly sources, returned in a three-tier ranking:

Tier 3 (top, "consensus and curated"): - CH — Harrison & Romhild's curated dataset (~58k links, OT-only as source). Hand-vetted; high-relevance pairs flagged canonical-direction. - Gage parallel — the tighter pairings from Warren Gage's John ↔ Revelation typological reading (Bradley/Gage, John/Rev only). - TSK ≥100 votes — TSK pairs with crowd-source consensus that strong are near-universal cross-references (top ~0.4% of TSK) and break through to compete with curated.

Tier 2 ("argued and acknowledged"): - Burnett — David A. Burnett's argued chain for the Gen 15:5 / Rom 4:18 "star-like seed" deification reading (JSPL 5.2, 2015). ~30 pairs. - Gage chiastic — the looser-typology sheet of Bradley/Gage (the source spreadsheet labels these "looser connections, just noting"). - TSK 20–99 votes — solid topical links acknowledged across commentaries (top ~5%).

Tier 1 (long-tail): TSK <20 votes — surface only when explicitly raising limit for exhaustive study.

Use this BEFORE drawing any theological conclusion from a single verse — results frequently surface the texts the original verse is quoting, the fulfilment passages, contested parallel readings, and the chain of NT authors who picked the verse up.

By theme. Pass theme="atonement" (or salvation_by_grace, deity_of_christ, resurrection, holy_spirit, justification) to get a hand-curated chain of foundational passages for that doctrine. Use this when the user asks a broad theological question without anchoring to a specific verse.

Important caveat about coverage. TSK is built on R.A. Torrey's 19th-century index, which catalogues topical/thematic connections — not necessarily direct quotations or verbal allusions. Consequence: a verse with few cross-refs here is NOT necessarily a verse with few biblical echoes. Famously, Revelation shows surprisingly few links to OT prophetic books even though it is saturated with OT symbolism, because Torrey indexed by subject and Revelation's subject is "apocalyptic". The CH dataset partly compensates (it leans toward NT-quotes-OT linking), so when you suspect a quotation/ allusion is being missed, retry with source="ch" or use find_similar_passages to catch verbal parallels the topical index would skip.

Adaptive default — limit is a CAP, not a target. Default limit=8. The tool returns rows in tier-then-strength order and SUPPRESSES tier-1 noise (low-vote TSK) by default whenever the verse has at least 3 rows from tier 2+. So:

• Signal-rich anchors return 6–8 strong refs spanning curated, scholarly, and consensus-TSK sources.

• Signal-poor anchors return only what passes the bar — fewer rows is the correct answer, not a bug. Don't pad your reasoning with weak refs.

To pull the long tail (only when the user explicitly asks for exhaustive study): pass source="tsk" (returns all TSK including tier 1) or min_strength=0 (treats as explicit "I want some long-tail too"). Either disables tier-1 suppression. Pair with a higher limit (20–30).

How to interpret the scores you get back. Each row carries type (the dataset), relevance (its native strength signal), and where applicable a tsk_votes side-channel showing the TSK count for that pair. You MUST read these before using a ref:

TSK vote scale (full corpus distribution): ≥ 500 votes — extraordinary; near-universal cross-reference (top 0.01%, only 35 pairs) 100-499 — very strong; the link tradition reflexively makes (top 0.4%) 50-99 — strong; well-established parallel (top 1.3%) 20-49 — solid; real connection acknowledged across commentaries (top 5%) 10-19 — moderate; one of many recognised links (top 12%) 5-9 — weak; thematic stretch, use with caution (top 33%) 2-4 — very weak; mostly noise floor (62% of TSK) 0-1 — noise

CH (curated — all CH refs carry signal, but the tag tells you weight): "canonical direction" (rel=3 or 2) — Harrison's flag for the canonical direction of the pair, often part of a thematic circle (top 78% of CH) no tag (rel=0) — present in CH but unflagged (still hand-curated)

Gage (John ↔ Revelation typology): relevance=3 ("parallel" tier) — tighter pairings from the parallel-reading of John 1 ↔ Revelation 1 relevance=1 ("chiastic" tier) — looser thematic echoes across the full John-Revelation chiasm; the source spreadsheet flags these as "looser connections, just noting" The note field carries the thematic tags + commentary + per-row attribution (Bradley vs Gage). Treat as canonical-typology, not topical.

Burnett (single-paper argued chain): All Burnett rows are at relevance=5 by convention — they're explicit claims from one scholar's published argument, not graded by strength. The note field carries the JSPL citation and which step of the argument the pair belongs to. Cite Burnett by name when surfacing these to the user; they're a scholarly proposal, not consensus.

When the top results are weak, SAY SO. If the strongest ref returned has only 5-15 votes, do not present it with the same confidence as a 200-vote parallel. Caveat the answer: "this verse isn't strongly cross-referenced in the topical index — the closest link is X with only N votes, suggesting tradition didn't treat this as a major thematic anchor." When TSK is thin, try source="ch" — Harrison's curated set leans toward NT-quotes-OT links and may catch what a topical index missed. Or fall back to find_similar_passages for verbal/semantic parallels Torrey wouldn't index.

You may pass source="ch" or source="tsk" to restrict to one dataset — useful when CH alone gives too little (e.g. an obscure verse with no CH coverage) or when you want the dense TSK long-tail.

USE THIS when any biblical person, place, or thing is mentioned.

This is your PRIMARY TOOL for thematic linking across the Bible. The database contains 4,000+ biblical persons and 1,000+ places with rich relationship data.

RELATIONSHIP DATA ENABLES THEMATIC CONNECTIONS:

• Parents: Trace lineages backward (e.g., David → Jesse → Obed → Boaz → Salmon)

• Children: Trace lineages forward (e.g., Abraham → Isaac → Jacob → 12 tribes)

• Siblings: Connect related narratives (e.g., Moses ↔ Aaron ↔ Miriam)

• Spouse: Connect family narratives (e.g., Ruth → Boaz → David's lineage)

THEMATIC LINKING EXAMPLES:

1. Messianic lineage: lookup Abraham → David → Solomon → ... → Joseph/Mary

2. Priesthood lineage: lookup Aaron → Eleazar → Phinehas → ... → Zadok

3. Geographic connections: lookup Bethlehem for its role in Ruth, David, and Jesus narratives

4. Prophecy fulfillment: trace how places mentioned in OT prophecy appear in NT

When answering questions about biblical characters or places, ALWAYS check their relationships to find connections that enrich your answer with biblical context.

This grounds character discussions in the actual biblical data rather than just training recall.

Explain a morphological/grammatical parsing code.

For Greek: Robinson codes (e.g., 'V-AAI-3S' = Verb, Aorist, Active, Indicative, 3rd person, Singular) For Hebrew: Westminster/OpenScriptures codes

Returns full grammatical explanation including part of speech, person, number, tense, voice, mood, case, and gender where applicable.

USE THIS after word_study to show how a word is actually used.

After identifying a key Greek/Hebrew word (via word_study or search_lexicon), use this to find actual verses where it appears. This shows:

• How biblical authors used the word in context

• Range of meanings through actual examples

• Key passages for that term

This transforms word study from definition into demonstration.

Find passages with similar semantic content to a given Bible verse.

USE THIS to discover thematic connections across the Bible that may not be captured by explicit cross-references or shared vocabulary. This tool uses vector embeddings to find passages with similar meaning, not just similar words.

EXAMPLES OF DISCOVERIES:

• Daniel 7:13-14 (Son of Man vision) → Revelation 1:7, 14:14 (similar imagery)

• Exodus 12:1-13 (Passover) → John 1:29, 1 Corinthians 5:7 (Lamb imagery)

• Isaiah 53:4-6 (Suffering Servant) → 1 Peter 2:24-25 (echoes of Isaiah)

• Proverbs wisdom themes → James practical wisdom

⚠️ CRITICAL HERMENEUTICAL WARNING: Semantic similarity does NOT equal theological connection or relevance. Two passages may use similar language but have completely different meanings based on their literary context, historical setting, and authorial intent.

BEFORE USING SIMILAR PASSAGES IN YOUR RESPONSE, YOU MUST:

1. Check Genre Compatibility: A prophetic vision and a historical narrative may share imagery but require different interpretive approaches. Use lookup_verse to understand each passage's genre.

2. Verify Historical Context: What did this passage mean to its original audience? Similar language across centuries may have different referents.

3. Examine Literary Context: Is the similar passage using the language literally, metaphorically, or as an allusion? A quote vs. independent usage matters greatly.

4. Apply Fee & Stuart's Questions:

   • What did this text mean to the original readers?

   • What is the author's stated purpose?

   • How does this fit the book's overall argument/narrative?

5. Distinguish Types of Similarity:

   • Direct quotation (explicit OT in NT)

   • Deliberate allusion (author intentionally echoing)

   • Shared tradition (common Jewish/Christian concepts)

   • Coincidental similarity (similar words, unrelated meaning)

Only present a similar passage as theologically relevant if you can establish an actual interpretive connection, not mere semantic overlap.

Takes a verse reference (with pre-computed embedding) and returns semantically similar passages ranked by similarity score.

ALWAYS USE THIS when a question involves family lineage, ancestry, descendants, or tribal identity.

This tool traverses multi-generational family trees using genealogical data for 1,100+ biblical persons. Unlike lookup_name (which shows immediate family), this traces lineage across many generations.

WHEN TO USE (instead of lookup_name):

• "Who was David's father?" → lookup_name is enough for one generation

• "Trace the line from Abraham to David" → USE THIS — traverses multiple generations

• "What tribe was Paul from?" → USE THIS — traces tribal ancestry

• "Show me Jesus' genealogy" → USE THIS — traces the full Messianic lineage

• "How does Ruth connect to the line of David?" → USE THIS

Returns a family tree with generation numbers, relationship types, and a Mermaid diagram. ALWAYS include the Mermaid diagram in your response so the user can visualize the family tree.

ALWAYS USE THIS when studying or explaining a Bible passage to identify WHO is present and WHERE it takes place.

Returns all people, places, and events mentioned in a passage according to the Theographic Bible Metadata. This is essential context for passage study — you cannot properly explain a passage without knowing its cast.

USE THIS WHEN:

• Studying any narrative passage (e.g., "Who is in Genesis 22?" → Abraham, Isaac, angel of the LORD, Moriah)

• Explaining a chapter (e.g., "What's happening in Acts 15?" → shows Paul, Barnabas, James, Jerusalem, Antioch)

• A user asks "Tell me about [passage]" → use this alongside lookup_verse for complete context

DIFFERENCE FROM graph_enriched_search:

• people_in_passage: works on chapters AND verses, returns entity lists

• graph_enriched_search: verse-level only, but adds family relationships for each person found

ALWAYS USE THIS when a user asks about a biblical person's life, biography, or timeline.

Returns every recorded event in a person's life in chronological order, with locations and dates. This is the ONLY tool that shows what happened in someone's life and in what order.

USE THIS WHEN:

• "Tell me about Moses" → shows his entire life: birth, burning bush, exodus, Sinai, death on Nebo

• "What did Paul do?" → shows conversion, missionary journeys, imprisonment, Rome

• "What happened to David?" → anointing, Goliath, fleeing Saul, kingship, Bathsheba, death

• Any biographical question about a biblical figure

COMBINE WITH lookup_name (for identity/relationships) and explore_genealogy (for lineage). Returns a Mermaid timeline diagram — ALWAYS include this in your response.

ALWAYS USE THIS when a user asks about a biblical location or its significance.

Returns the complete biblical history of a place: events that occurred there, people born/died there, and geographic data. Shows how a location threads through salvation history across multiple eras.

USE THIS WHEN:

• "Tell me about Jerusalem" → shows events from Salem/Melchizedek through David, Solomon, exile, Jesus

• "What happened at Bethlehem?" → Ruth & Boaz, David's birthplace, Jesus' birth, Micah's prophecy

• "Why is Mount Sinai important?" → shows all events: burning bush, law given, golden calf, Elijah

• "What is the significance of [any place]?" → always use this

• Any question about biblical geography or a specific location

DIFFERENCE FROM lookup_name with type="place":

• lookup_name: returns basic place info and immediate connections

• explore_place: returns FULL history — every event, every person, across all biblical periods

Returns a Mermaid network diagram — ALWAYS include this in your response.

ALWAYS USE THIS when a user asks how two biblical people are related or connected.

Traces the shortest family relationship path between any two people in the biblical genealogies. Uses parent, child, sibling, and spouse relationships to find the connection.

USE THIS WHEN:

• "How are Ruth and David related?" → shows Ruth → Obed → Jesse → David

• "What's the connection between Abraham and Moses?" → traces through Levi

• "Are Paul and Barnabas related?" → checks for any family connection

• Any question comparing two biblical figures or asking about their relationship

DIFFERENCE FROM explore_genealogy:

• explore_genealogy: shows one person's family tree (ancestors/descendants)

• find_connection: finds the PATH between two specific people

Returns a Mermaid flowchart — ALWAYS include this in your response.

USE THIS for deep study of a specific verse — combines the verse text with all relational context.

Returns the verse text PLUS all people, places, and events mentioned in it, PLUS family relationships for each person found. This is the most comprehensive single-query tool for studying a specific verse.

USE THIS WHEN:

• Deep-diving into a single verse (e.g., "Explain Genesis 22:1 in detail")

• Preparing a sermon or Bible study on a specific text

• You need verse text + entity context in one call (saves calling lookup_verse + people_in_passage separately)

Example: graph_enriched_search("Matthew 1:1") returns:

• Verse text: "The book of the genealogy of Jesus Christ, the son of David, the son of Abraham"

• People found: Jesus, David, Abraham — with their family relationships

• Places and events associated with the verse

DIFFERENCE FROM people_in_passage:

• people_in_passage: works on chapters AND verses, returns entity lists only

• graph_enriched_search: verse-level only, but includes verse text AND family relationships

Get scholarly study notes and translation notes for a Bible verse or chapter.

Returns combined commentary from:

• Tyndale Study Notes: Concise, verse-level scholarly commentary (66 books)

• UW Translation Notes: Translator-focused commentary with linguistic insights

• SIL Translator Notes: Additional translation and cultural context

USE THIS when you need:

• Scholarly commentary on a specific verse

• Help explaining difficult passages

• Translation and cultural background notes

• Chapter-level overview of themes and context

This provides published, peer-reviewed scholarship rather than AI-generated commentary.

Look up a topic in the Tyndale Bible Dictionary.

Contains 500+ topical articles covering:

• Biblical people and places

• Theological concepts and doctrines

• Cultural practices and customs

• Historical background

• Archaeological findings

USE THIS when you need:

• Background information on a biblical topic

• Historical or cultural context for a passage

• Detailed article about a person, place, or concept

• Scholarly definition of a theological term

Returns the full dictionary article with cross-references.

Look up a key theological term in the FIA Key Terms database.

Contains 200+ carefully defined theological and biblical terms with:

• Clear definitions accessible to translators

• Biblical usage and context

• Cross-references to related terms

• Translation guidance

USE THIS when you need:

• A precise definition of a theological term (agape, atonement, justification, etc.)

• To understand how a concept is used across Scripture

• Translation-oriented explanation of a term

• Cross-references to related theological concepts

Get Ancient Near East (ANE) cultural and historical background for a biblical passage.

The biblical authors and their audiences lived in the Ancient Near East with fundamentally different assumptions about cosmology, social structure, religion, law, and daily life. This tool retrieves structured ANE contextual data to illuminate what the text meant to its original audience.

USE THIS when:

• Studying creation, flood, or cosmological texts (three-tier universe, cosmic waters)

• Encountering divine council, heavenly assembly, or "sons of God" language

• Reading about the serpent, Eden, the fall, or spiritual warfare passages

• Encountering references to temples, sacrifices, or religious practices

• Studying meal, table, or eating passages (fellowship, allegiance, covenant meals)

• Encountering household, family, or father language applied to God

• Reading about covenants, treaties, or legal codes (suzerainty treaties, lex talionis)

• Studying honor/shame dynamics in Gospels or Epistles

• Understanding marriage customs, family structures, or inheritance laws

• Reading about warfare, kingship, or imperial contexts

• Studying Levitical purity, clean/unclean categories, or scapegoat rituals

• Encountering literary forms (chiasm, inclusio, lament, oracle)

• Needing background on daily life, agriculture, or material culture

• Encountering "soul," "spirit," nephesh, or ruach language (Hebrew vs. Greek anthropology)

• Any passage where modern Western assumptions might obscure the ANE meaning

• Needing the interpretive methodology (derivation hierarchy, confidence calibration)

13 dimensions: cosmology_worldview, religious_practices, social_structure, legal_covenant, political_imperial, economic_life, literary_conventions, warfare_military, daily_life_material_culture, death_afterlife, gender_family, education_literacy, ane_methodology

9 periods: patriarchal, exodus_conquest, judges_early_monarchy, united_monarchy, divided_monarchy, assyrian_babylonian, persian, hellenistic, roman

Call with NO arguments to see available dimensions and periods. Call with just a reference to get ALL relevant ANE context for a passage. Filter by dimension and/or period for focused results. Call with dimension='ane_methodology' to retrieve the derivation hierarchy, confidence calibration, and methodological guardrails for working with ANE parallels.

Get theological scholarship context for a Bible passage or theme.

Returns scholarly content from multiple authors (Heiser, Bradley, etc.) with verse mappings and theme links. When no author is specified, returns all scholars' content for the query — allowing side-by-side comparison.

USE THIS when discussing:

• The divine council (Psalm 82, Deuteronomy 32, Job 1-2) — Heiser

• Sons of God / bene elohim (Genesis 6, Job 38) — Heiser

• The Angel of Yahweh / two-powers theology — Heiser

• Nephilim, Rephaim, and the giant clans — Heiser

• The nachash / serpent in Eden (Genesis 3) — Heiser, Bradley

• Cosmic geography and spiritual warfare — Heiser

• Deuteronomy 32 worldview / allotment of nations — Heiser, Bradley

• Salvation, soteriology, the gospel, conversion, atonement — Bradley (theme: domain_transfer)

• The Fall, Genesis 3, sin entering the world — Bradley (theme: nested_household, corporate_headship)

• Life/death, light/darkness, righteousness/sin, love/pride and other biblical binary pairs — Bradley (theme: binary_hierarchy)

• Satan, the devil, spiritual warfare, the enemy, two kingdoms — Bradley (theme: pater_familias_binary)

• The sin-death connection, wages of sin, power of death — Bradley (theme: sin_death_satan_chain)

• Corporate solidarity, "in Adam" / "in Christ", federal headship — Bradley (theme: corporate_headship)

• Satan's imitation of God's kingdom, counterfeit worship — Bradley (theme: rival_counterfeits)

• Acts 26:17-18 and Paul's commission — Bradley (theme: domain_transfer)

Query by verse reference, theme key, and/or author.

Get the structurally-paired verses for a Torah passage under Moshe Kline's Woven Torah hypothesis.

The Torah is organised as 86 two-dimensional literary units (Genesis–Deuteronomy). Each unit is a grid of cells arranged in rows and columns, and cells are deliberately paired with one another across rows (horizontal partners) and down columns (vertical partners). Knowing the weave partners of a verse gives you additional passages that the Torah's author(s) intended to be read alongside it.

USE THIS when:

• Studying any passage in Genesis, Exodus, Leviticus, Numbers, or Deuteronomy

• You want to see which other verses are structurally paired with a passage

• You suspect two passages in the Torah are deliberately interwoven (doublets, creation/flood, law parallels, etc.)

• You're preparing a comparative reading and want the author-intended partners, not just thematic cross-references

• You want additional context for a Torah verse beyond lexical or thematic similarity

WHAT IT RETURNS:

• The literary unit the verse sits in (title, format, type, verse span)

• The cell the verse occupies (row/column label + verse range)

• Horizontal partner cells (same row, same subdivision, different column)

• Vertical partner cells (same column, same subdivision, different row)

• Sibling cells (same row and column, adjacent subdivisions)

• A short explanation of what each direction of pairing means under Kline's method

• A directive block instructing the caller how to turn these pointers into an interpretation

HOW TO USE THE OUTPUT: This tool returns STRUCTURAL POINTERS, not pre-written interpretation. After calling it, call lookup_verse on each partner cell's verse range to read the actual text, then synthesise the interpretation yourself using the directional semantics the tool provides. Horizontal partners are symmetric parallels (same register, different thematic tracks); vertical partners trace a progression through divine-name registers along a single thematic track. Reading the paired verses and applying those semantics is how the weave yields meaning.

Only Torah books (Genesis through Deuteronomy) have weave data. Source: Moshe Kline, chaver.com, CC BY 4.0.

USE THIS whenever a New Testament writer quotes an OT verse and the wording does not match the Masoretic Hebrew Text — or whenever lookup_verse emits the LXX-quotation hint.

WHAT IT RETURNS for a given verse reference:

• The Masoretic Hebrew (MT) reading + original Hebrew

• The variant reading (typically the LXX form quoted in the NT, or a DSS reading that differs from MT)

• The variant's original-language form (Greek or Hebrew)

• Manuscript witnesses for each reading (LXX, DSS scrolls — e.g. 1QIsa^a, 4QDeut^q, Mur88 — Masoretic Text, NT quotation citation)

• Scholarly consensus on which reading is older / how the divergence arose

• The HLT preferred reading (which form the Heiser Literal Translation follows) + the rationale

The HLT's principle: when the NT directly quotes the LXX form of an OT verse, the LXX form is the authoritative reading for Christian Scripture — apostolic endorsement overrides text-critical priority. So for verses like Psalm 40:6 / Hebrews 10:5, Isaiah 61:1 / Luke 4:18, Amos 9:12 / Acts 15:17, the HLT follows the LXX form in the body and footnotes the MT.

USE THIS when:

• Explaining why a NT OT quotation does not match the modern English OT

• Discussing Hebrews 10:5-7, Hebrews 1:6, Matthew 12:20-21, Acts 15:17, Luke 4:18-19, Luke 3:6, Matthew 21:16, Romans 9:27-29, Romans 10:20, Romans 15:12, Romans 2:24, Acts 7:43, Acts 8:32-33, Acts 13:41, 1 Peter 4:18, Ephesians 4:26, Luke 3:36, or the OT verses they quote

• The user asks "did the Masoretes edit Christ out?" — point them at the actual textual data instead of speculation

• Working on HLT translation for any verse where the NT follows a different form than the Hebrew

PAIRS WITH: lookup_verse (which emits a hint pointing here when a verse has a quote-hint or variant row).