Skip to main content
Glama

get_passage

Read a Bible passage in one or more editions side by side (Hebrew WLC, Greek Septuagint, SBL Greek NT, English WEB/King James/ASV/Douay-Rheims/Brenton, Russian Synodal, Luther 1912, Louis Segond). Reference numbering is WEB, or WEB Classic for additional books it holds, otherwise Brenton. source_numbering identifies native verses. Unestablished correspondences are flagged aligned:false with no counterpart text.

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": {
      "ref": "<ref>"
    },
    "name": "get_passage"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYese.g. "JHN.1.1-5", "Genesis 14:18-20", "PSA.110", "Tobit 14:4"
editionsNoEdition ids from list_editions, e.g. ["hebrew","lxx","en"]. Defaults to the reference edition: en, web-full or lxx-en for that book.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / editions / description
      Previous value: -"Edition ids from list_editions, e.g. [\"hebrew\",\"lxx\",\"en\"]. Default [\"en\"]."New value: +"Edition ids from list_editions, e.g. [\"hebrew\",\"lxx\",\"en\"]. Defaults to the reference edition: en, web-full or lxx-en for that book."
    • changedInput schema / properties / ref / description
      Previous value: -"e.g. \"JHN.1.1-5\", \"Genesis 14:18-20\", \"PSA.110\""New value: +"e.g. \"JHN.1.1-5\", \"Genesis 14:18-20\", \"PSA.110\", \"Tobit 14:4\""
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses which numbering scheme governs the reference, that native verse numbering is exposed via source_numbering, and that unestablished cross-edition correspondences surface as aligned:false with no counterpart text. It stops short of describing overall return shape or how books/verses missing from an edition are handled.

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?

Three tight, front-loaded sentences with no filler; the core purpose leads and the numbering/alignment caveats follow. Slight density of internal jargon ('source_numbering', 'WEB Classic', 'aligned:false') that a cold reader must infer, but nothing is wasted.

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 read tool with no annotations and no output schema, the definition covers the essential semantics: what is read, which editions, how references resolve, and what a failed correspondence looks like. Remaining gaps (full response structure, missing-verse behavior) are secondary for a retrieval tool.

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 both parameters are already documented, including the list_editions pointer and the default edition logic. The description adds real interpretive value for 'ref' by explaining which numbering system resolves ambiguous references, but 'editions' gains little beyond the schema's own default explanation.

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 description opens with a concrete verb and resource — 'Read a Bible passage' — and scopes it to 'one or more editions side by side,' enumerating the specific editions available. An agent can immediately tell this is the content-retrieval tool rather than an enumeration tool like list_editions, though it never explicitly names a sibling it is not.

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

Usage Guidelines3/5

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

Usage is implied by the read-shaped purpose, and the description clarifies reference format expectations ('Reference numbering is WEB, or WEB Classic...'), but it gives no explicit when-to-use/when-not-to-use guidance and never points to list_editions for discovering edition ids (that pointer lives only in the schema).

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.

Resources