Skip to main content
Glama
GodfreyPrince

studybible-tamil-mcp

by GodfreyPrince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_theology_context

Read-onlyIdempotent

Retrieve theological scholarship context for a Bible passage or theme from multiple authors, with verse mappings and theme links for side-by-side comparison.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum entries to return. Default: 10
themeNoTheme key (e.g., 'divine_council', 'pater_familias_binary', 'domain_transfer', 'sin_death_satan_chain')
authorNoFilter by author: 'heiser', 'bradley', 'owen', 'stott', 'lennox'. Omit to get all scholars' content.
referenceNoBible reference (e.g., 'Psalm 82:1', 'Genesis 6:2', 'Acts 26:18', 'John 8:44')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/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 safety is covered. The description adds non-annotation context: aggregation across authors, the author-omitted comparison behavior, and that results carry verse mappings and theme links. It stops short of describing pagination or result ordering.

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

Conciseness4/5

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

Front-loaded with purpose and return behavior, then the coverage list. The list is long but each bullet pairs a topic with its author and theme key, so it earns its space as query-construction reference rather than padding.

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?

With no output schema, the description carries the return-value burden, and it does state the content shape (scholarly content per author, verse mappings, theme links). Limits and defaults come from the schema. Adequate for an agent to call correctly, though result ordering/format detail is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies. The description goes beyond the schema by mapping real topics to the exact 'theme' keys and 'author' values that hold them (e.g., domain_transfer/bradley, penal_substitution/owen), which materially helps an agent compose valid queries.

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?

States a specific verb and resource ('Get theological scholarship context for a Bible passage or theme') and immediately names the return shape (multiple authors, verse mappings, theme links). The topic coverage list makes it unmistakably distinct from siblings like get_bible_dictionary, get_ane_context, and get_study_notes.

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?

Explicitly explains query modes ('Query by verse reference, theme key, and/or author') and the key behavioral fork: omitting author returns all scholars for side-by-side comparison. It lacks explicit when-not-to-use guidance or routing against the 22 sibling tools, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools