Skip to main content
Glama

uiule

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Verse

get_verse
Read-onlyIdempotent

Get a specific Bible verse or range by reference (e.g., "john 3:16", "romans 8:28", "psalm 23:1-6"). Returns verse text in World English Bible translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesBible reference string (e.g. "john 3:16", "genesis 1:1-3", "psalm 23"). Spaces will be encoded automatically.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesFull verse 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 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "reference": "john 3:16"
+  },
+  {
+    "reference": "psalm 23:1-6"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only and idempotent, so the description does not need to restate that. The description adds valuable behavioral context by specifying that the text is returned in the World English Bible translation, which goes beyond the schema.

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 concise sentences, front-loaded with the action and resource, and includes useful examples. Every word earns its place with no redundancy or fluff.

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 simple tool with one parameter and an output schema, the description is largely complete, covering purpose, examples, and translation. It does not mention error handling or explicitly differentiate from similar sibling tools, but these are minor gaps given the tool's simplicity.

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 input schema already provides full coverage and examples for the 'reference' parameter, including automatic space encoding. The description reinforces the reference format but does not add significantly new meaning beyond what the schema documents.

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 clearly states the tool retrieves a specific Bible verse or range by reference, with concrete examples. However, it does not explicitly differentiate itself from the sibling tool 'get_passage', which may cause ambiguity about which tool to use for passage lookups.

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?

The description gives clear context on valid reference formats and the translation used, implicitly suggesting when to use this tool. However, it does not explicitly state when to use it over alternatives like 'random_verse' or 'search_within'.

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