Skip to main content
Glama

bible_compare

Read-only

Compare one NT verse word-by-word across the Greek editions (byzantine Majority Text, tr Textus Receptus, sblgnt critical text) and list the textual differences. Accentuation/case are ignored (byzantine/tr are stored unaccented), so reported differences are real variants or spelling variants (e.g. movable Ny). Additionally reports per-word attestation across eight editions (NA27/28, Tyndale House, SBL, Westcott-Hort, Tregelles, TR, Byzantine; STEPBible TAGNT). Use for questions about textual variants (e.g. the Comma Johanneum, 1Jn 5:7). OT verses have only one edition (WLC) and cannot be compared. To find WHICH verses of a chapter differ before comparing them one by one, call bible_compare_chapter.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "book": "<book>",
      "chapter": "<chapter>",
      "verse": "<verse>"
    },
    "name": "bible_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesNT book name in German (e.g. "Römer", "1Joh")
verseYesSingle verse number
chapterYesChapter number

Output Schema

NameRequiredDescriptionDefault
hinweisYes
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
spracheYes
warnungNoThe TAGNT attestation contradicts the edition text here. Belongs in the answer about this verse, not in a footnote.
bezeugungNo
editionenYes
referenceYes
vergleicheYes
bezeugung_fehltNoWhy `bezeugung` is absent for this verse. A gap in the source, not a statement about the verse.
quellenkonflikteNoPer affected form, what the edition actually reads. The edition text governs, not the TAGNT note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds genuinely useful behavior beyond that, notably that accentuation and case are ignored because byzantine/tr are stored unaccented, so reported differences may be spelling variants like movable Ny. It also discloses the eight-edition attestation output. It stops short of describing ordering or edge-case failure behavior, so not a 5.

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?

Front-loaded with the core action and the normalization caveat, then routing advice last. The parenthetical list of eight editions is somewhat dense, but every sentence carries operational information.

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?

For a three-parameter read tool with full schema coverage, an output schema, and annotations covering the safety profile, the description supplies everything needed: scope, normalization caveats, OT exclusion, and the correct sibling for a different task.

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 book/chapter/verse, including the German book-name convention. The description reinforces the single-verse scope and the NT-only constraint on book names, but adds little parameter-level detail beyond 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?

States a specific verb and resource: compare one NT verse word-by-word across three named Greek editions and list textual differences. It also clearly distinguishes itself from the sibling bible_compare_chapter, which finds differing verses across a chapter rather than detailing one verse.

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?

Explicitly names the use case (textual-variant questions such as the Comma Johanneum), states a hard exclusion (OT verses have only WLC and cannot be compared), and routes the agent to bible_compare_chapter when it wants to find which verses differ first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.