Skip to main content
Glama

bible_original

Read-only

Return one Bible verse, or up to 10 verses of one chapter, word-by-word in the ORIGINAL language with lemma, Strong's number and full morphology. Use this to verify what the original text says — e.g. whether a noun is singular or plural — instead of inferring it from a translation. Pass verse for one verse or verses for several in one call. Covers the whole Bible: the OT (book 1–39) is served from the Hebrew/Aramaic Westminster Leningrad Codex; the NT (40–66) from a Greek text type chosen via texttyp — "byzantine" (Majority Text, default), "sblgnt" (critical), or "tr" (Textus Receptus, the only one with the Comma Johanneum). Edition and text type are labelled in the output.

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_original"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesBook name in German (e.g. "1. Mose", "Jesaja", "Römer", "Galater")
verseNoSingle verse number
versesNoSeveral verses of the chapter instead of `verse`: range "16-18" or list "1,3,5", at most 10 verses per call. Each word then carries its `vers`.
chapterYesChapter number
texttypNoNT text edition: "byzantine" (Majority Text, default), "sblgnt" (critical SBL), or "tr" (Textus Receptus). Ignored for the OT (always Hebrew WLC). Compare byzantine vs. tr to see TR-only readings such as the Comma Johanneum (1Joh 5,7).byzantine

Output Schema

NameRequiredDescriptionDefault
editionYes
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
texttypYes
woerterYes
referenceYes
verse_ohne_datenNoRequested verses this edition does not carry. `reference` names the verses that are in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / verses
      Added value: +{
      +  "description": "Several verses of the chapter instead of `verse`: range \"16-18\" or list \"1,3,5\", at most 10 verses per call. Each word then carries its `vers`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "book",
      -  "chapter",
      -  "verse"
      -]New value: +[
      +  "book",
      +  "chapter"
      +]
    • addedOutput schema / properties / verse_ohne_daten
      Added value: +{
      +  "description": "Requested verses this edition does not carry. `reference` names the verses that are in the response.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / woerter / items / properties / vers
      Added value: +{
      +  "description": "The verse this word belongs to. Present only in a multi-verse response.",
      +  "type": "integer"
      +}
  2. 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 real context beyond them: full Bible coverage, the OT/NT source distinction, the 10-verse-per-call limit, and that edition and text type are labelled in the output. It does not cover error behavior for unknown German book names or out-of-range verses, which keeps it below 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-loads the purpose in one sentence, then parameter routing, then source coverage — a logical order with little padding. It is on the dense side, with the text-type enumeration somewhat repeating the schema, but no sentence is clearly wasted.

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 5-parameter read-only tool with a full output schema and annotations, the description covers what the tool returns, where the text comes from per testament, the call-size limit, and how to select a text type. An agent has enough to invoke it correctly without opening the schema.

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

Parameters4/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, but the description adds meaning beyond the schema by stating the canonical book numbering (OT 1–39, NT 40–66) and tying `texttyp` to a concrete verification use case (Comma Johanneum in 1Joh 5,7). Most of the per-parameter semantics are nonetheless restated from the schema rather than extended.

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: return Bible verses word-by-word in the original language with lemma, Strong's number and morphology. The phrase 'instead of inferring it from a translation' implicitly separates it from translation-lookup siblings, and the OT/NT source split (WLC Hebrew/Aramaic vs. Greek text type) makes the resource scope unambiguous.

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 a concrete usage scenario (verify whether a noun is singular or plural in the original) and a negative instruction not to infer grammar from a translation. It also routes between the `verse` and `verses` parameters and explains which `texttyp` to pick for TR-only readings. It stops short of naming a specific sibling tool as the alternative, so not a full 5.

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.