Skip to main content
Glama
djayatillake

Study Bible MCP Server

by djayatillake
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_theology_context

Read-onlyIdempotent

Obtain theological scholarship and contextual notes for Bible passages or themes. Compare insights from multiple authors by querying reference, theme, or author.

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.

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.

Input Schema

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

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, non-destructive, and idempotent. The description adds context about returning all authors' content when none specified and that results include verse mappings and theme links. This adds some value, but no additional safety or behavioral details beyond annotations.

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?

The description is relatively long due to the extensive use case list, but it is well-structured with a clear opening sentence listing the main purpose, followed by bullet point examples. It remains focused on the tool's functionality without unnecessary filler.

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?

Without an output schema, the description briefly notes that results include scholarly content with verse mappings and theme links, which is sufficient for understanding the return type. Parameters are well-covered, and no required fields reduce complexity. Overall, it provides enough context for correct usage.

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 covers all four parameters (reference, theme, author, limit) with descriptions, so baseline is 3. The description provides concrete examples (e.g., 'Psalm 82:1', 'divine_council') and explains the effect of omitting author, enhancing semantic value.

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 clearly states the tool retrieves theological scholarship context for Bible passages or themes, specifying authors and content types. It distinguishes itself from siblings like 'get_ane_context' or 'get_bible_dictionary' by focusing on specific scholars (Heiser, Bradley) and providing verse mappings and theme links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists numerous use cases (e.g., 'divine council', 'sons of God') and maps them to authors. It also explains behavior when no author is specified, giving clear guidance on when to use this tool versus others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djayatillake/studybible-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server