Skip to main content
Glama

uiule

by io.github.pipeworx-io

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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. Dates show when Glama detected each change.

  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: +[
+  {}
+]
  3. First observed

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 uiule toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but ask_pipeworx and ask_pipeworx_grounded are very similar and could cause confusion. The multiple Polymarket tools are differentiated by their specific functions.

Naming Consistency3/5

Tool names are a mix of verb_noun (e.g., ask_pipeworx, get_verse) and noun_verb (e.g., polymarket_arbitrage, ai_visibility_check). While all use snake_case, the pattern is inconsistent.

Tool Count4/5

With 33 tools, the server is comprehensive but slightly large. Each tool seems justified, covering multiple domains like company data, prediction markets, Bible, and memory.

Completeness5/5

The tool surface is highly complete for a universal data server, including financials, drugs, patents, news, real estate, and more. Meta-tools like discover_tools and suggest_questions further enhance usability.

Resources