Skip to main content
Glama

bible_compare_chapter

Read-only

Overview of a whole NT chapter (or a verse range): WHICH verses differ between the loaded Greek editions (byzantine, tr, sblgnt), and in what words. One call instead of comparing verse by verse. Lists only the differing verses with the differing edition pairs, counts per pair, and marks verses where the TAGNT apparatus notes a meaning variant. It does not classify a difference and carries no per-word attestation: for a verse of interest call bible_compare. NT only.

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>"
    },
    "name": "bible_compare_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesNT book name in German (e.g. "Römer", "1Joh")
versesNoOptional: restrict to verses, range "1-12" or list "3,7,9". Omit for the whole chapter.
chapterYesChapter number

Output Schema

NameRequiredDescriptionDefault
paareYesPer edition pair, how many of the checked verses differ.
verseYesOnly the verses that differ, each with only the pairs that differ.
hinweisYes
kurzrefYes
quellenYes
spracheYes
editionenYes
identischNoVerse list of the checked verses on which all loaded editions agree.
referenceYesThe verses that were checked.
verse_geprueftYes
verse_ohne_datenNo
verse_mit_unterschiedYesVerses that differ in at least one edition pair. Take this number; do not count the list.
tagnt_bedeutungsvariantenNoVerse list of all checked verses where the TAGNT apparatus notes a meaning variant, whether or not the loaded editions differ there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare a safe read (readOnlyHint true, openWorldHint false); the description goes well beyond them by disclosing the result shape (only differing verses, differing edition pairs, per-pair counts, TAGNT apparatus meaning-variant marks). It also states what the tool does NOT do (no classification, no per-word attestation) and scopes it to NT, which prevents misuse.

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

Conciseness5/5

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

Front-loaded with the scope, then the result contents, then the boundary and the alternative tool. Every clause carries information — the negative scoping sentences ('does not classify', 'no per-word attestation') actively steer the agent away from wrong expectations despite the dense telegraphic style.

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 an output schema present, return structure need not be spelled out, yet the description still summarizes it. Combined with the NT-only constraint, the verses narrowing, and the pointer to bible_compare, nothing an agent needs to invoke this correctly is 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 schema already documents all three parameters including the verses range/list syntax. The description only adds that a verse range narrows the overview and that books are NT-only; it contributes little parameter meaning beyond the structured fields, so the baseline of 3 applies.

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 concrete verb and resource ('Overview of a whole NT chapter ... WHICH verses differ between the loaded Greek editions') and enumerates the loaded editions (byzantine, tr, sblgnt). It explicitly distinguishes itself from bible_compare by scope, so an agent can tell the two apart without opening either schema.

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?

Gives the selecting condition directly: 'One call instead of comparing verse by verse' and 'for a verse of interest call bible_compare.' Both the when-to-use and the explicit alternative are named, plus the NT-only restriction.

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.