Skip to main content
Glama

Bibelstudium MCP

by de.bibelstudium-mcp

bible_lookup

Read-only

Look up Bible verses by reference. Returns exact text from a licensed German translation (see the translation argument for this instance's default). Use this for ALL Bible quotes — never quote from memory. When the edition carries footnotes for the requested verses, the field 'fussnoten' holds them verbatim: these are the publisher's own notes, not this server's, and they typically record an alternative rendering the edition weighed. Also call it when a book or reference looks unfamiliar, misspelled or made up, and before answering whether a book exists or belongs to the canon: the error names the nearest known book and states which canon this database covers. Do not answer such questions from memory either — a reference that seems wrong is a reason to call this tool, not to skip it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookYesBook name in German (e.g. "Jesaja", "1. Mose", "Römer", "Ps", "Mt")
versesNoVerse(s): single "4", range "16-17", list "1,3,5", or combined "1-3,7". Omit for the whole chapter. Some editions cap how many verses one call may quote; the response then says so in `hinweis` and `gekuerzt`, and `reference` names what it contains.
chapterYesChapter number
translationNoTranslation: "LUT" (Luther 1912), "SCH" (Schlachter 1951), "ELB" (Elberfelder 1871), "MB" (Menge 1939), "SLT" (Schlachter 2000). Default: "SLT" (Schlachter 2000). Aliases like "luther", "schlachter" accepted. Only editions this instance actually loaded can be requested; bible_server_info lists them.SLT

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
hinweisNo
kurzrefYesSame reference in the short German citation form ("2Kor 8,9.13-15"). Copy this into prose; `reference` spells the book out and is not the citation form.
quellenYes
gekuerztNo
fussnotenNo
referenceYes
translationYes

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses additional behavioral traits: footnotes are returned in the 'fussnoten' field with provenance, truncation can occur with `hinweis` and `gekuerzt`, and error responses name the nearest known book and canon coverage. This goes well 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 front-loads the core purpose and then adds high-value usage rules and edge-case handling. While slightly verbose, every sentence earns its place—no filler or repetition. It could be tightened slightly, but it remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, the description covers footnotes, truncation, error behavior, canon questions, and memory-safety. With a rich output schema and readOnly/openWorld annotations, the description fully equips an agent to use the tool appropriately across normal and edge-case scenarios.

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

Parameters3/5

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

Schema coverage is 100% and all parameters have detailed descriptions, so the schema carries the heavy lifting. The description adds minimal param-specific value beyond referencing the default translation and hinting that translation availability is instance-dependent, but this does not materially enhance the schema's meaning.

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 opens with a specific verb and resource: 'Look up Bible verses by reference.' It clearly differentiates from sibling tools by stating it is for ALL Bible quotes and never to quote from memory, positioning it as the canonical lookup tool.

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?

Explicit when-to-use guidance is given: 'Use this for ALL Bible quotes — never quote from memory.' It also instructs to call the tool when a reference looks unfamiliar or before answering canon questions, and explicitly warns against skipping the tool for seemingly wrong references. This provides strong contextual usage direction.

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

All Bibelstudium MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation4/5

The tools are mostly distinct: bible_lookup retrieves text by reference, bible_search finds by words, bible_original gives original-language detail, bible_compare compares Greek editions, bible_concordance does word studies, bible_crossrefs provides cross-references, and bible_server_info reports server data. There is slight potential for confusion between bible_original and bible_compare since both deal with original languages, but their purposes are clearly delineated.

Naming Consistency5/5

All tools follow a consistent 'bible_' prefix followed by a single descriptive verb (lookup, search, original, compare, concordance, crossrefs, server_info). The pattern is uniform and predictable, making it easy to infer tool purpose from the name alone.

Tool Count5/5

Seven tools is well-scoped for a Bible study server. Each tool covers a core function (looking up, searching, original text, comparison, concordance, cross-references, and server info) without redundancy, and the count is in the ideal range for maintainability and clarity.

Completeness4/5

The tool set appears comprehensive for typical Bible study needs: retrieval, search, original-language analysis, textual comparison, concordance, cross-references, and server metadata. Minor gaps exist, such as no direct tool for retrieving full chapter text or parallel reading across translations (though bible_lookup can retrieve multiple verses), and no support for OT textual comparison since only one edition exists; these are acceptable limitations.

Resources