Skip to main content
Glama

bible_lookup_many

Read-only

Look up SEVERAL Bible passages in ONE call: exact text for up to 30 references, each with its own book, chapter, verses and optionally its own translation (the same passage in two translations is two entries). Use this instead of several bible_lookup calls whenever more than one passage is needed. Results come back in request order; an entry that fails carries fehler and does not fail the others. Never quote from memory: an entry without text was not delivered. Editions that cap verbatim quoting apply the cap to the whole call (all entries of that edition together); entries beyond it come back with ohne_wortlaut and no text, and hinweis says so.

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": {
      "stellen": "<stellen>"
    },
    "name": "bible_lookup_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
stellenYesThe passages, 1 to 30 entries, answered in this order.
translationNoTranslation for all entries that do not name their own: "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
hinweisNo
quellenYes
stellenYesOne entry per requested passage, in request order. An entry carries either `text`, or `fehler`, or `ohne_wortlaut`.
gekuerztNo
angefragtYes
geliefertYesEntries that carry `text`.
ohne_wortlautYesEntries beyond a verbatim cap, without text.
fehlgeschlagenYesEntries that carry `fehler`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint false), and the description adds genuinely useful behavior: results return in request order, a failing entry carries `fehler` without failing the others, and quoting caps apply call-wide so overflow entries return `ohne_wortlaut` with a `hinweis`. The 'Never quote from memory' warning reinforces that a missing `text` means nothing was delivered. What keeps it below a 5 is that some of this (the `fehler`/`ohne_wortlaut`/`hinweis` fields) is effectively explaining the return shape, which the output schema may already declare.

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?

The batch scope and the replacement-for-bible_lookup rule are front-loaded in the first two sentences, and the remaining sentences cover ordering, partial failure, and quoting caps — each carrying distinct operational information. No filler or restatement of the name.

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?

For a two-parameter batch tool with an output schema, this covers what an agent needs: capacity limit, ordering guarantee, partial-failure semantics, and quoting-cap behavior with the named sentinel fields. The only thing an agent might still want is guidance on what to do on receiving `ohne_wortlaut`, though the 'never quote from memory' line largely implies it.

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 coverage is 100%, so the baseline is 3; the description still earns a bump by stating the 30-entry ceiling up front and clarifying that a per-entry translation overrides the call-wide one, plus that two translations of the same passage are two entries. It stops short of restating verse-range syntax or translation codes, which the schema already handles well.

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?

The description opens with a specific verb and resource — 'Look up SEVERAL Bible passages in ONE call' — and immediately scopes it to 'exact text for up to 30 references' with per-entry book, chapter, verses and optional translation. It distinguishes itself from the sibling bible_lookup by framing this as the batched variant, so an agent can choose 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?

Explicit routing rule: 'Use this instead of several bible_lookup calls whenever more than one passage is needed,' which names the alternative and the threshold that selects it. It also clarifies a subtle case — the same passage in two translations counts as two entries — removing ambiguity about whether to call once or twice.

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.