Skip to main content
Glama
GodfreyPrince

studybible-tamil-mcp

by GodfreyPrince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_ane_context

Read-onlyIdempotent

Retrieve Ancient Near East cultural and historical background for any Bible passage. Clarifies original audience assumptions about cosmology, law, worship, family, and warfare.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoHistorical period to filter by
dimensionNoANE dimension to filter by (e.g., 'cosmology_worldview', 'legal_covenant')
referenceNoBible reference (e.g., 'Genesis 1:1', 'Deuteronomy 5:1', 'Matthew 5:1')
detail_levelNoOutput detail level. 'brief' = title + summary + significance for all entries. 'standard' (default) = full detail for direct chapter matches, brief for broad/whole-book matches. 'full' = full detail for all entries.standard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so safety is covered. The description adds real behavioral detail beyond that: no-argument calls return the available dimensions and periods, a reference alone returns all matching context, and the ane_methodology dimension returns the derivation hierarchy and confidence calibration. It doesn't describe result size or pagination, but for a local read-only tool this is solid.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is bloated: a 17-bullet list that includes vague catch-alls ('Any passage where modern Western assumptions might obscure the ANE meaning'), plus a full re-enumeration of the 13 dimensions and 9 periods that the input schema already defines as enums. Those enumerations are pure duplication and could be dropped.

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?

No output schema exists, but the description explains return behavior and detail-level semantics well enough for an agent to call the tool correctly, and annotations cover the operation's safety profile. Only minor gaps remain (result volume, how hits are keyed to a reference).

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 description coverage is 100%, so baseline is 3. The description earns above baseline by explaining the default/empty-argument behavior (returns available dimensions and periods), how dimension and period narrow the result set, and the special semantics of 'ane_methodology' — none of which the schema conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ('Get Ancient Near East (ANE) cultural and historical background for a biblical passage') and the scope is unmistakably distinct from most siblings. However, it never names or contrasts with plausibly-confusable siblings such as get_bible_dictionary, get_theology_context, or get_torah_weave, leaving the agent to infer the boundary.

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?

The 17-item 'Relevant to passages involving...' list is essentially an explicit when-to-use trigger catalogue, which is unusually actionable. It lacks any when-not-to-use or alternative-routing guidance (e.g., 'for lexical data use word_study instead'), 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