Skip to main content
Glama

List Bible editions

list_editions
Read-onlyIdempotent

The Bible editions available, with language and licence: osnb (Norwegian Bokmål), osnn (Norwegian Nynorsk), osen (English), oses (Spanish) are open CC BY 4.0 translations made by the free-bible project directly from the Hebrew and Greek; sblgnt (Greek New Testament), tanach (Hebrew Old Testament) are the source texts; kjv (King James Version, English), web (World English Bible), bsb (Berean Standard Bible, English), asv (American Standard Version, English), luther_1912 (Luther 1912, German), segond_1910 (Louis Segond 1910, French), rv_1909 (Reina-Valera 1909, Spanish), akjv (American King James Version, English), albanian (Albanian Bible), bungo (Bungo-yaku, classical Japanese), cadman (Cadman 1926, Vietnamese), chinese_union_simp (Chinese Union Version, simplified), chinese_union_trad (Chinese Union Version, traditional), cpdv (Catholic Public Domain Version, English), dbt (Darby Translation, English), diodati (Diodati, Italian), drb (Douay-Rheims (Challoner), English), elberfelder_1905 (Elberfelder 1905, German), elberfelder_1871 (Elberfelder 1871, German), dnb30 (Bibelselskapet 1930, Norwegian Bokmål), erv (English Revised Version), finn (Finnish 1776), geneva (Geneva Bible, English), hcv (Haitian Creole Bible (1985)), he_modern (Modern Hebrew Bible (Delitzsch NT)), jps (JPS Tanakh 1917, English), kougo (Kougo-yaku 1954/55, Japanese), lv_gluck_8 (Glück Bible, Latvian), martin (Martin 1744, French), opt (Old Persian Version, Persian), rv_1858 (Reina-Valera 1858 New Testament, Spanish), sagradas (Sagradas Escrituras 1569, Spanish), slt (Smith's Literal Translation, English), swahili (Swahili New Testament), synodal (Synodal Translation 1876, Russian), tagab (Ang Biblia 1905, Tagalog), wbt (Webster Bible 1833, English), weymouth (Weymouth New Testament 1903, English), ylt (Young's Literal Translation, English), bn_irv (Indian Revised Version, Bengali), gu_irv (Indian Revised Version, Gujarati), irv (Indian Revised Version, Hindi), ha_con (Open Hausa Contemporary Bible), ha_lit (Litafi Mai-tsarki, Hausa New Testament), kn_irv (Indian Revised Version, Kannada), mr_irv (Indian Revised Version, Marathi), pa_irv (Indian Revised Version, Punjabi), ta_irv (Indian Revised Version, Tamil), te_irv (Indian Revised Version, Telugu), coverdale (Coverdale Bible 1535, English), tyndale (Tyndale Bible 1526/1534, English), svd (Smith-Van Dyck 1865, Arabic), my_judson (Judson Bible 1840, Burmese) are open translations, public domain or CC BY-SA — list_editions gives each one's licence and the credit it requires.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and idempotency are covered structurally. The description does add genuinely useful behavioral context beyond that: that entries carry licence terms (CC BY 4.0, public domain, CC BY-SA) and the attribution each requires, which matters for downstream use. It stops short of describing the shape of the returned entries beyond licence and credit, so it is additive but not rich.

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

Conciseness2/5

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

The description is a single enormous sentence dominated by roughly 55 edition-code/language pairs, none of which an agent needs in order to decide to call a zero-parameter listing tool. The genuinely useful parts (licence categories, attribution requirement) are buried after the bulk, so it is both over-long and badly back-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter, read-only listing tool this is arguably more than enough raw content, and it does disclose that licence and credit information come back, which is the one non-obvious return characteristic. What it omits is the thing that would actually help: that these codes are the identifiers accepted by other Bible tools. Without an output schema, the description should carry that linkage, and it does not.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. However, the description spends its length enumerating what looks like the tool's output values inside the description text rather than in an output schema, which blurs the boundary between parameter semantics and return-value documentation; a 3 reflects that this content belongs elsewhere and the description adds no parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific resource and scope: 'The Bible editions available, with language and licence', and the closing sentence restates that list_editions returns each edition's licence and required credit. However, the middle of the description is an undifferentiated enumeration of edition codes rather than a statement of purpose, which dilutes the clarity of the verb+resource framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this tool, e.g. 'use this to discover valid edition codes before calling search_bible or get_passage', and no mention of when not to use it. The agent must infer the discovery role from the catalog content itself, which is implied usage at best and is not tied to any named sibling.

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.