Skip to main content
Glama

Bibelstudium MCP

by de.bibelstudium-mcp

bible_crossrefs

Read-only

Find cross-references (related/parallel passages) for one Bible verse, ranked by relevance votes, with the German text of the targets (in editions that cap verbatim quoting, the later targets carry stelle and votes only). Use this to find where a theme, quote or promise recurs elsewhere in Scripture. Where the UBS Parallel Passage Database lists the verse, parallelen adds the closed set of parallel places (synoptic pericopes, Kings/Chronicles doublets, OT quotations in the NT, recurring formulas) that the vote ranking often buries. Data: Treasury of Scripture Knowledge (expanded), OpenBible.info, CC-BY; UBS Parallel Passage Database, CC BY-SA 4.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookYesBook name in German (e.g. "Jesaja", "1. Mose", "Römer")
limitNoMaximum number of references to return (default 10, max 30)
verseYesSingle verse number
chapterYesChapter number
translationNoTranslation for the quoted target texts: "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
gesamtYesNumber of references that exist for this verse, independent of `limit`. Larger than `verweise.length` means the list was cut; take this number, do not derive one from the list.
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
verweiseYes
referenceYes
parallelenNoPresent only when the UBS Parallel Passage Database lists this verse. A group is an unordered set with no direction and no ranking, unlike `verweise`; a verse can belong to more than one group.
lesehinweisNo

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the readOnlyHint annotation: relevance-vote ranking, German text of targets, the quoting-cap caveat where later targets carry only `stelle` and `votes`, and the closed-set `parallelen` behavior from the UBS database. It also discloses data sources and licenses.

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 dense but well-structured, with the core purpose front-loaded. Every sentence contributes something useful, though the data-license clause is secondary to invocation and could be trimmed without losing essential guidance.

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?

With a full input schema, an output schema, and read-only annotations, the description covers the tool's core behavior, special cases, usage rationale, and data provenance. Nothing needed to call the tool correctly appears missing.

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 description coverage is 100%, so the baseline is 3. The description adds useful context about German target text and translation editions but does not materially enhance the per-parameter meaning already present in the schema.

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 states a specific action and resource: find cross-references (related/parallel passages) for one Bible verse, ranked by relevance votes, with German target text. This clearly distinguishes it from sibling tools like bible_search, bible_compare, or bible_lookup.

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?

It gives explicit guidance: 'Use this to find where a theme, quote or promise recurs elsewhere in Scripture.' It also explains when the `parallelen` field is most valuable. However, it does not explicitly mention when not to use it or name alternative siblings.

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