Skip to main content
Glama

uiule

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesBible reference string (e.g. "john 3:16", "genesis 1:1-5")
translationYesTranslation code: "web" (default), "kjv", "oeb-us", "bbe", "webbe", "cherokee", "dra"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesFull passage text
versesYesArray of verse objects with book, chapter, verse, and text
referenceYesBible reference string
translationYesTranslation ID code
translation_nameYesFull name of the translation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "reference": "john 3:16",
+    "translation": "kjv"
+  },
+  {
+    "reference": "genesis 1:1-5",
+    "translation": "web"
+  }
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description's addition of 'Returns full text with reference and translation metadata' goes beyond the safety profile by disclosing the return format. This useful context compensates for lacking details about rate limits or auth, which are less critical for a read-only tool.

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 description is two sentences, front-loaded with the core action, and every word contributes meaning. It lists translations efficiently and states the return type without fluff, making it highly concise and well-structured.

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?

For a simple read-only tool with two fully documented parameters, an output schema, and comprehensive safety annotations, the description covers the essential purpose, customizability, and return behavior. No significant gaps remain for an agent to use it correctly.

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%, fully documenting both parameters with examples and translation codes. The description adds minimal value by listing translations in prose, but it does not provide any syntax details beyond the schema, so the baseline of 3 is appropriate.

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 ('Get') and identifies the resource ('Bible passage') with translation options, clearly distinguishing it from tools like random_verse and implying specific reference-based retrieval. It mentions the output includes full text and metadata, making the tool's function unmistakable.

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?

The description does not provide any when-to-use or when-not-to-use guidance, nor does it mention alternatives like get_verse for single verses. The context is limited to what the tool does, without positioning it among sibling tools.

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

All uiule toolsInspect
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.

Resources