Bible

Random Verse

random_verse

Read-onlyIdempotent

Fetch a random Bible verse from the World English Bible (WEB) translation. Returns the reference, full verse text, translation ID, and per-verse breakdown with book, chapter, and verse number.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`text`	Yes	Full verse 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.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "reference": {
+      "description": "Bible reference string",
+      "type": "string"
+    },
+    "text": {
+      "description": "Full verse 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: +[
+  {}
+]
```
First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful context by specifying the return payload: reference, full verse text, translation ID, and per-verse breakdown. No contradictions with annotations.

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 sentences, zero wasted words. Every piece of information (action, translation, return format) earns its place, and the description is front-loaded with the core purpose.

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?

The description fully covers what this simple tool does and returns, and an output schema exists to handle structured return details. No parameters or edge cases need explanation. The tool is self-contained even without sibling comparison.

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?

The tool has zero parameters, so the schema is trivially complete. The description does not need to explain parameters, and the baseline for zero-parameter tools is 4.

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 uses a specific verb ('Fetch') and a clear resource ('a random Bible verse'), and specifies the translation (World English Bible). It distinguishes itself from siblings like get_verse and get_passage by emphasizing randomness, making its purpose unambiguous.

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

Usage Guidelines4/5

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

The description clearly implies when to use this tool (when a random verse is desired) through the word 'random'. However, it does not explicitly mention alternatives or when not to use it, so it misses the 'explicit alternative' criterion for a 5.

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.