Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STUDY_BIBLE_TAMIL_DBNoPath to the SQLite database file. If not provided, defaults to `data/study_bible_tamil.db` relative to the server installation. Use this to specify a custom location.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
word_studyA

Look up the lexicon entry for a Strong's number, or for a Greek, Hebrew, or English word.

Given a Strong's number (G26, H430) the entry is returned directly; given an English word, the most relevant Greek or Hebrew term is resolved first.

Returns:

  • The word in its original script (e.g. ἀγάπη, אֱלֹהִים)

  • Transliteration and pronunciation

  • Strong's number

  • Brief and full definitions (LSJ for Greek, BDB for Hebrew, plus Abbott-Smith for NT Greek where available)

  • Etymology, semantic range, and related words

  • Occurrence counts and representative passages

Relevant for questions about a specific original-language term, a theological term's underlying vocabulary, or the semantic range behind an English rendering.

lookup_verseA

Look up the text of a Bible verse or verse range, in English and in the original language.

Returns:

  • The English verse text

  • The original Greek/Hebrew text (optional, on by default)

  • A word-by-word breakdown with Strong's numbers and glosses

  • Optional grammatical parsing for each word

  • Genre-specific interpretive background for the passage's literary type

  • Availability notes for related data (cross-references, Torah weave partners, and NT/OT LXX-quotation variants) where the verse has such records

Accepts references such as 'John 3:16', 'Gen 1:1', or 'Romans 3:21-26'.

Relevant whenever the verified wording of a passage, or its original-language form, is needed.

search_lexiconA

Search the Greek and Hebrew lexicons by English word, transliteration, or concept.

Returns the matching lexicon entries ranked by relevance — typically several distinct original-language words that an English term covers (e.g. "love" → agapē, phileō, erōs), each with its Strong's number, definition, and semantic range.

Relevant for identifying which original-language terms lie behind an English word or a biblical concept, and for distinguishing between near-synonyms.

get_cross_referencesA

Retrieve the cross-references for a Bible reference — the passages traditionally read alongside it — or a curated chain of passages for a doctrinal theme.

Two 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.

Results typically include the texts the verse quotes, its fulfilment passages, contested parallel readings, and the later 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 — relevant for broad theological questions not anchored to a specific verse.

Coverage caveat. 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 source="ch" may surface a quotation or allusion the topical index misses, as may find_similar_passages for verbal parallels.

Adaptive default — limit is a cap, not a target. Default limit=8. Rows are returned in tier-then-strength order, and tier-1 noise (low-vote TSK) is suppressed 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; a short result set means the verse has few well-attested links, not that the query failed.

For the long tail, source="tsk" returns all TSK rows including tier 1, and min_strength=0 sets an explicit floor of zero. Either disables tier-1 suppression; both pair with a higher limit (20–30).

Interpreting the scores. 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. The scales differ by dataset:

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; the tag indicates 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. They represent a single scholarly proposal rather than consensus.

A result whose strongest row has only 5–15 votes indicates a verse the topical index does not treat as a major thematic anchor — a materially weaker signal than a 200-vote parallel. For such verses source="ch" (Harrison's curated set, which leans toward NT-quotes-OT links) and find_similar_passages (verbal/semantic parallels Torrey did not index) cover different ground.

The source parameter restricts results to a single dataset — useful when CH alone gives too little coverage for an obscure verse, or when the dense TSK long-tail is wanted.

lookup_nameA

Look up general information about a biblical person, place, or thing by name — Abraham, David, Bethlehem, and so on.

Covers 4,000+ biblical persons and 1,000+ places. Returns the entry's original-language name, description, key verse references, ACAI annotations where available (variant names, roles, reference and speech counts), and its immediate relationships:

  • Parents — one generation back (e.g. David → Jesse)

  • Children — one generation forward (e.g. Abraham → Isaac)

  • Siblings (e.g. Moses ↔ Aaron ↔ Miriam)

  • Spouse (e.g. Ruth ↔ Boaz)

Relevant for identifying a named figure or location and for the immediate family and reference context around it. Multi-generation lineages are covered by explore_genealogy, a person's life events by explore_person_events, and a location's full history by explore_place.

parse_morphologyA

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.

search_by_strongsA

Search by Strong's number for every verse where that word appears.

Takes a Strong's number (typically obtained from word_study or search_lexicon) and returns the passages containing that Greek or Hebrew word, showing how biblical authors used it in context and the range of senses it carries across occurrences.

find_similar_passagesA

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

Takes a verse reference (one with a pre-computed embedding) and returns semantically similar passages ranked by similarity score. Matching is by vector embedding rather than shared vocabulary, so it surfaces connections that explicit cross-reference indexes and word searches miss.

Typical results:

  • 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

What the similarity score does and does not mean. The score measures proximity in embedding space, which is not evidence of a theological or authorial connection. Two passages can share vocabulary and imagery while differing in genre, historical setting, referent, and authorial intent. The returned set mixes several distinct phenomena that the score cannot tell apart: direct quotation (an explicit OT citation in the NT), deliberate allusion, shared tradition (common Jewish or Christian concepts), and coincidental verbal overlap between unrelated texts.

Establishing which of these applies to a given pair requires the passages' genre, historical setting, and literary context — lookup_verse returns genre background, get_study_notes and get_ane_context cover context and original audience, and get_cross_references indicates whether the link is attested in the cross-reference tradition.

explore_genealogyA

Trace a genealogy: a biblical person's ancestors and/or descendants across multiple generations of lineage.

Traverses genealogical data covering 1,100+ biblical persons. Returns a family tree with generation numbers and relationship types, plus a Mermaid diagram of the tree.

Covers questions such as tracing the line from Abraham to David, a person's tribal ancestry, the Messianic lineage, or how a figure connects into a known line. For a single generation (e.g. one person's father), lookup_name returns immediate family without the traversal.

people_in_passageA

List the people, places, and events mentioned in a Bible passage.

Returns the entities recorded for a chapter or verse in the Theographic Bible Metadata — for example, Genesis 22 returns Abraham, Isaac, the angel of the LORD, and Moriah; Acts 15 returns Paul, Barnabas, James, Jerusalem, and Antioch.

Relevant for establishing the cast and setting of a narrative passage. Related tools: graph_enriched_search is verse-level only but adds the verse text and family relationships for each person found.

explore_person_eventsA

Retrieve the recorded events of a biblical person's life in chronological order.

Returns each event with its location and date where known, plus a Mermaid timeline diagram. Moses returns birth, burning bush, exodus, Sinai, and death on Nebo; Paul returns conversion, missionary journeys, imprisonment, and Rome.

This is the only tool covering event sequence and dating for a person. Related tools: lookup_name for identity and relationships, explore_genealogy for lineage.

explore_placeA

Retrieve the full biblical history of a place.

Returns the events recorded there, the people born or who died there, and geographic data, spanning all biblical periods — plus a Mermaid network diagram. Jerusalem returns events from Salem/Melchizedek through David, Solomon, the exile, and Jesus; Mount Sinai returns the burning bush, the giving of the law, the golden calf, and Elijah.

Relevant for questions about biblical geography or a location's significance across salvation history. Related tool: lookup_name with type="place" returns basic place info and immediate connections only.

find_connectionA

Trace the shortest family relationship path between two biblical people.

Walks parent, child, sibling, and spouse relationships in the biblical genealogies to find a connecting path, and returns it as a Mermaid flowchart. Ruth and David return Ruth → Obed → Jesse → David; Abraham and Moses trace through Levi. Where no family connection exists, that is reported.

Relevant for questions about how two named figures relate. Related tool: explore_genealogy returns one person's ancestors or descendants rather than a path between two people.

graph_enriched_searchA

Retrieve a comprehensive enriched view of a single verse: its text plus all people, places, events, and family relationships.

Returns the verse text, the people, places, and events mentioned in it, and the family relationships of each person found. For 'Matthew 1:1' that is the verse text, Jesus, David, and Abraham with their relationships, and the associated places and events.

Combines what lookup_verse and people_in_passage return separately. Verse level only; people_in_passage also accepts chapters but returns entity lists without verse text or relationships.

get_study_notesA

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

Relevant for published commentary on a specific verse, difficult passages, translation and cultural background, and chapter-level overviews of themes and context. The content is published scholarship, quoted as-is with source attribution.

get_bible_dictionaryA

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

Relevant for background on a biblical topic, historical or cultural context, a detailed article on a person, place, or concept, or a published definition of a theological term.

Returns the full dictionary article with cross-references.

get_key_termsA

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

Relevant for a precise definition of a theological term (agape, atonement, justification, and similar), how a concept is used across Scripture, a translation-oriented explanation, or cross-references to related concepts.

get_ane_contextA

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 on what the text meant to its original audience.

Relevant to passages involving:

  • 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

With no arguments, returns the available dimensions and periods. With a reference alone, returns all ANE context matching that passage. The dimension and period parameters narrow the result set. The dimension 'ane_methodology' returns the derivation hierarchy, confidence calibration, and methodological limits that apply to ANE parallels generally.

get_theology_contextA

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.

Coverage by topic, with the author and theme keys that hold it:

  • 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)

  • Penal substitution, propitiation, definite/particular atonement, imputed righteousness, justification — Owen, Stott (themes: penal_substitution, propitiation, definite_atonement, justification_imputation)

  • Mortification of indwelling sin, sanctification, communion with God, the glory of Christ — Owen (themes: mortification_of_sin, sanctification, communion_with_god, glory_of_christ)

  • Christ's high priesthood, the new covenant, Hebrews — Owen (themes: high_priesthood, new_covenant)

  • The cross of Christ, the four images of salvation, the self-substitution of God — Stott (theme: atonement_models, reconciliation)

  • The Sermon on the Mount, kingdom ethics, the Holy Spirit's fullness (baptism vs filling) — Stott (themes: kingdom_ethics, holy_spirit_work)

  • Genesis 1 and science, creation, the days debate — Lennox (theme: creation_genesis)

  • Providence, God's sovereignty and human freedom, the problem of evil (Joseph, Daniel) — Lennox (themes: providence, divine_sovereignty_freedom)

  • Faithful witness in a hostile culture, Daniel — Lennox (theme: faithful_witness)

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

get_torah_weaveA

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). A verse's weave partners are therefore the passages the hypothesis holds the Torah's author(s) intended to be read alongside it.

Relevant to any passage in Genesis, Exodus, Leviticus, Numbers, or Deuteronomy — particularly for identifying which verses are structurally paired with a passage, for suspected deliberate interweaving (doublets, creation/flood, law parallels), and for comparative readings where the pairing claimed is compositional rather than thematic.

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

The output is a set of structural pointers — verse ranges and their pairing direction — not pre-written interpretation. The text of the partner cells is not included; lookup_verse returns it. Under Kline's method horizontal partners are symmetric parallels (same divine-name register, different thematic tracks) and vertical partners are a progression through registers along a single thematic track; the thematic content of each column is not labelled in Kline's dataset.

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

get_textual_variantA

Retrieve the textual variant record for a verse where the Masoretic Hebrew, the Septuagint, and/or the Dead Sea Scrolls diverge.

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.

Relevant where a New Testament quotation does not match the modern English Old Testament, and to questions about how the Hebrew, Greek, and Qumran textual traditions differ at a specific verse.

Covered verses include 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, and the Old Testament verses they quote. Either side of a pair returns the same variant row.

lookup_verse reports when a verse has a quotation hint or variant row.

search_tamil_versesA

Search the Tamil Bible text (Tamil IRV, full 66 books) for words or phrases.

Returns verses whose Tamil text matches every search token, ranked by relevance. Use for finding where the Tamil Bible uses a given Tamil word (e.g. 'கிருபை', 'பரிசுத்த ஆவி', 'ராஜ்யம்'), for Tamil concordance work, and for locating verses from remembered Tamil wording. Tamil renderings of the found verses pair well with word_study and search_by_strongs for original-language follow-up.

Optional 'book' filter narrows results to one book (e.g. 'Jhn', 'Psa').

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 22 tools

Disambiguation4/5

Most tools target distinct data sources or operations, but a few boundaries require reading descriptions: lookup_verse vs graph_enriched_search, people_in_passage vs graph_enriched_search, and word_study vs search_lexicon vs search_by_strongs. The descriptions mitigate this with explicit 'Related tools' guidance and scope notes.

Naming Consistency3/5

All names use snake_case, but the verb pattern is mixed (get_, lookup_, search_, explore_, find_, parse_) and a few are noun phrases such as word_study and people_in_passage. The naming is readable but not a predictable verb_noun convention throughout.

Tool Count4/5

22 tools is on the high side for a single MCP server, but each maps to a distinct Bible-study dataset or operation rather than redundant functionality. Reasonable for a comprehensive study Bible, though a tighter grouping could reduce surface area.

Completeness5/5

The surface covers verse lookup, original languages, lexicons, morphology, cross-references, semantic parallels, dictionaries, ANE and theology background, genealogies, people/place/event exploration, textual variants, and Tamil full-text search. No obvious dead ends for a study Bible domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues