Sovereign Logos Scripture

Find reply verses

find_reply_verses

Read-onlyIdempotent

Find verses and matching images for a debate or reply. Search by word, phrase, topic or reference (e.g. "mammon", "idols", "false prophets", "Isaiah 7:14"); returns curated topics with anchor verses, a ready verse-image URL for each, and the topic's backgrounds. Topics: mammon, money-changers, only-way, narrow-way, seed-is-christ, new-covenant, septuagint, false-teachers, hypocrisy, idolatry, moloch, judgment, sodom, marriage, christ-is-king, sword, antichrist, persecution, nephilim, the-cross, resurrection, repentance, work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_reply_verses"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Word, phrase, topic slug or reference. Empty returns every topic.
`format`	No

Output Schema

Name	Required	Description	Default
`query`	Yes
`topics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "type": "string"
+    },
+    "topics": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "verses": {
+            "items": {
+              "properties": {
+                "imageUrl": {
+                  "type": "string"
+                },
+                "reference": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "reference"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "slug",
+          "label",
+          "verses"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "topics"
+  ],
+  "type": "object"
+}

AddedNov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description's added value is the curated-topic nature and the fact that each topic carries a prebuilt image URL and backgrounds, but since an output schema exists, restating return contents earns limited credit. No rate limits, permissions, or failure behavior are mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and efficient, but it is followed by an enumeration of 23 topic slugs that largely duplicates what the schema already promises (an empty query returns every topic). That list is token-heavy for information the agent can retrieve by calling the tool with no arguments.

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 two-parameter read-only lookup with annotations and an output schema, the description covers purpose, accepted query forms, and result shape well. The only meaningful omission is the meaning of the `format` enum values, which an agent needs to choose an image aspect ratio 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 50%: `query` is already documented and the description usefully adds concrete example values ("mammon", "idols", "Isaiah 7:14"). The `format` enum (feed/square/story) is undocumented in both the schema and the description, leaving a real gap the description does not compensate for.

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 states a specific verb and resource ("Find verses and matching images") and scopes it to "a debate or reply", with explicit search modes (word, phrase, topic, reference) and a clear statement of what comes back (curated topics with anchor verses, a ready verse-image URL, backgrounds). It implicitly separates itself from general scripture search by emphasizing curated debate topics, though it never names a sibling tool outright.

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?

It conveys the input styles it accepts and gives concrete query examples, which implies when to reach for it, but there is no explicit when-not guidance and no routing to alternatives such as search_scripture or create_verse_image. An agent must infer that this is the curated-topic path rather than the general lookup path.

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

All Sovereign Logos Scripture 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.

Resources

Need Help?