studybible-tamil-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STUDY_BIBLE_TAMIL_DB | No | Path 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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:
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:
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 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
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 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 Adaptive default —
For the long tail, Interpreting the scores. Each row carries 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 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 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 The |
| 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:
Relevant for identifying a named figure or location and for the immediate
family and reference context around it. Multi-generation lineages are covered by
|
| 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 |
| 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:
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 — |
| 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), |
| 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: |
| 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: |
| 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: |
| 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:
|
| 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 |
| get_study_notesA | Get scholarly study notes and translation notes for a Bible verse or chapter. Returns combined commentary from:
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:
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:
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:
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:
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 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; 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 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.
|
| 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 Optional 'book' filter narrows results to one book (e.g. 'Jhn', 'Psa'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
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.
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.
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.
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.