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

Name	Required	Description	Default
`book`	Yes	Book name in German (e.g. "Jesaja", "1. Mose", "Römer")
`limit`	No	Maximum number of references to return (default 10, max 30)
`verse`	Yes	Single verse number
`chapter`	Yes	Chapter number
`translation`	No	Translation 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

Name	Required	Description
`gesamt`	Yes	Number 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.
`hinweis`	No
`kurzref`	Yes	Same 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.
`quellen`	Yes
`gekuerzt`	No
`verweise`	Yes
`reference`	Yes
`parallelen`	No	Present 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.
`lesehinweis`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 2, 2026
- addedOutput schema / properties / gekuerzt / properties / parallelen_entfallen
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / gekuerzt / properties / parallelen_gezeigt
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / gekuerzt / properties / parallelen_max
```
Added value: +{
+  "description": "Only when the parallel passages hit their own, smaller budget; the share of verse_max they may use at most.",
+  "type": "integer"
+}
```

Changed1 schema field changedAug 22, 2026

addedOutput schema / properties / parallelen

Added value: +{
+  "description": "Present 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.",
+  "properties": {
+    "gruppen": {
+      "items": {
+        "properties": {
+          "stellen": {
+            "items": {
+              "properties": {
+                "locator": {
+                  "description": "The reference exactly as the UBS source writes it (USFM book code). In the Old Testament the source counts verses after the Hebrew Bible while this server follows its German editions; where the two differ, this string is authoritative and `stelle` is the resolved approximation.",
+                  "type": "string"
+                },
+                "sprache": {
+                  "type": "string"
+                },
+                "stelle": {
+                  "type": "string"
+                },
+                "text": {
+                  "description": "Absent once the verbatim quota reserved for parallels is used up, and absent when the verses are missing from this translation.",
+                  "type": "string"
+                },
+                "verse_einzeln": {
+                  "items": {
+                    "properties": {
+                      "nr": {
+                        "type": "integer"
+                      },
+                      "text": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "nr",
+                      "text"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "zaehlung_abweichend": {
+                  "description": "Present and true only where the Hebrew text and the requested edition count this chapter differently, so `stelle` may be off by a verse or more. Absence is not a clearance: it also means the check could not run because the Hebrew text is not loaded.",
+                  "type": "boolean"
+                }
+              },
+              "required": [
+                "stelle",
+                "locator",
+                "sprache"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "stellen"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "stellen": {
+      "description": "Number of parallel places across all groups, the queried verse excluded.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "gruppen",
+    "stellen"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses ranking by relevance votes, the caveat that later targets may carry only stelle and votes in verbatim-quote-capping editions, and the special parallelen addition from the UBS Parallel Passage Database. It also names data sources and licenses, which is useful behavioral context.

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?

Four sentences, with the main purpose front-loaded and each sentence adding distinct information. The parenthetical about verbatim quoting is dense but not wasteful.

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?

Covers the purpose, ranking behavior, the special UBS parallel set, and data provenance, while the output schema presumably documents the return structure. It lacks error-handling or invalid-input notes, but these are not critical for a read-only lookup tool.

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%, so the schema already documents all five parameters. The description adds some context about translation edition behavior and German target text, but it does not materially go beyond what the parameter descriptions already provide.

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: 'Find cross-references (related/parallel passages) for one Bible verse, ranked by relevance votes, with the German text of the targets'. This clearly identifies what the tool does and produces, and it is distinguishable from sibling tools like bible_lookup or bible_search by the cross-reference focus.

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?

Gives an explicit use case: 'Use this to find where a theme, quote or promise recurs elsewhere in Scripture.' It does not explicitly name alternative sibling tools, but this usage context plus the output type makes when-to-use clear.

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

All Bibelstudium MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.