Skip to main content
Glama

bible_lookup

Read-only

Look up Bible verses by reference. Returns exact text from a licensed German translation (see the translation argument for this instance's default). Use this for ALL Bible quotes — never quote from memory. When the edition carries footnotes for the requested verses, the field 'fussnoten' holds them verbatim: these are the publisher's own notes, not this server's, and they typically record an alternative rendering the edition weighed. Also call it when a book or reference looks unfamiliar, misspelled or made up, and before answering whether a book exists or belongs to the canon: the error names the nearest known book and states which canon this database covers. Do not answer such questions from memory either — a reference that seems wrong is a reason to call this tool, not to skip it. For two or more passages, or one passage in several translations, call bible_lookup_many once instead of this tool several times.

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

Input Schema

NameRequiredDescriptionDefault
bookYesBook name in German (e.g. "Jesaja", "1. Mose", "Römer", "Ps", "Mt")
versesNoVerse(s): single "4", range "16-17", list "1,3,5", or combined "1-3,7". Omit for the whole chapter. Some editions cap how many verses one call may quote; the response then says so in `hinweis` and `gekuerzt`, and `reference` names what it contains.
chapterYesChapter number
translationNoTranslation: "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

NameRequiredDescriptionDefault
textYes
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
fussnotenNo
referenceYes
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that errors name the nearest known book and state the canon this database covers, that footnotes are the publisher's own and appear verbatim in 'fussnoten', and that verse caps surface via 'hinweis'/'gekuerzt'/'reference'. That is substantial operational context an agent could not infer from annotations.

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 routing rule, and most sentences carry distinct information (footnotes provenance, error behavior, verse caps). The canon paragraph restates the no-memory rule twice, which is mild redundancy rather than wasted bulk.

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, the description still usefully pre-explains the notable return fields (fussnoten, hinweis, gekuerzt, reference) and the failure mode. For a 4-parameter read tool, an agent has everything needed to call it correctly and interpret edge cases.

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, verses and translation syntax. The description adds only a pointer to the 'translation' argument for this instance's default, which the schema also states; no new meaning about parameter interaction is contributed.

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 ('Look up Bible verses by reference') and immediately characterizes the output as exact text from a licensed German translation. It explicitly carves out the sibling boundary: multi-passage or multi-translation requests go to bible_lookup_many instead.

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 explicit when-to-use conditions: all Bible quotes, unfamiliar/misspelled/suspected-fake references, and canon-membership questions before answering. It also names the alternative (bible_lookup_many) with the exact condition that selects it, plus an explicit when-not ('do not answer from memory').

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.