Bible

Get Passage

get_passage

Read-onlyIdempotent

Get a Bible passage in your choice of translation (KJV, WEB, OEB, BBE, Cherokee, DRA, and more). Returns full text with reference and translation metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "john 3:16",
      "translation": "kjv"
    },
    "name": "get_passage"
  }
}

Input Schema

Name	Required	Description	Default
`reference`	Yes	Bible reference string (e.g. "john 3:16", "genesis 1:1-5")
`translation`	No	Translation code: "web" (default when omitted), "kjv", "oeb-us", "bbe", "webbe", "cherokee", "dra"

Output Schema

Name	Required	Description
`text`	Yes	Full passage text
`verses`	Yes	Array of verse objects with book, chapter, verse, and text
`reference`	Yes	Bible reference string
`translation`	Yes	Translation ID code
`translation_name`	Yes	Full name of the translation

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 14, 2026

changedInput schema / properties / translation / description

Previous value: -"Translation code: \"web\" (default), \"kjv\", \"oeb-us\", \"bbe\", \"webbe\", \"cherokee\", \"dra\""New value: +"Translation code: \"web\" (default when omitted), \"kjv\", \"oeb-us\", \"bbe\", \"webbe\", \"cherokee\", \"dra\""

changedInput schema / required

Previous value: -[
-  "reference",
-  "translation"
-]New value: +[
+  "reference"
+]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "reference": {
+      "description": "Bible reference string",
+      "type": "string"
+    },
+    "text": {
+      "description": "Full passage text",
+      "type": "string"
+    },
+    "translation": {
+      "description": "Translation ID code",
+      "type": "string"
+    },
+    "translation_name": {
+      "description": "Full name of the translation",
+      "type": "string"
+    },
+    "verses": {
+      "description": "Array of verse objects with book, chapter, verse, and text",
+      "items": {
+        "properties": {
+          "book": {
+            "description": "Book name",
+            "type": "string"
+          },
+          "chapter": {
+            "description": "Chapter number",
+            "type": "number"
+          },
+          "text": {
+            "description": "Verse text",
+            "type": "string"
+          },
+          "verse": {
+            "description": "Verse number",
+            "type": "number"
+          }
+        },
+        "required": [
+          "book",
+          "chapter",
+          "verse",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "reference",
+    "translation",
+    "translation_name",
+    "text",
+    "verses"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "reference": "john 3:16",
+    "translation": "kjv"
+  },
+  {
+    "reference": "genesis 1:1-5",
+    "translation": "web"
+  }
+]

First observedApr 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that a full text body with reference and translation metadata is returned, which overlaps with the existing output schema rather than adding new behavioral context such as error behavior for invalid references.

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?

Two short sentences, front-loaded with the action and resource, with no redundant or filler wording. Everything stated is relevant to selection.

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 two-parameter read tool with full schema coverage, complete annotations, and an output schema, the definition is adequate but thin. It leaves the default translation and invalid-reference handling unstated, so the agent gets no behavioral fallback beyond the structured fields.

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, and the description goes slightly beyond it by framing translation as a user choice with several named options plus "and more." It does not, however, state the default translation or the accepted reference range syntax itself.

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 gives a specific verb and resource ("Get a Bible passage") plus the translation dimension, so the agent knows exactly what it retrieves. It does not, however, differentiate itself from the sibling bible_get_verse or random_verse, which sound adjacent in function.

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 only implied: the examples and mention of a reference make it clear this is for looking up a specific passage by citation. There is no explicit when-to-use versus when-not guidance and no named alternative for random or single-verse retrieval.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bible tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.