Sovereign Logos Scripture

Search scripture

search_scripture

Read-onlyIdempotent

Find verses containing a phrase (case-insensitive substring match) in one translation. Returns up to 50 hits in canonical order with references and links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_scripture"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of verses to return, 1 to 50. Default 20.
`query`	Yes	Word or phrase to find, 3 to 100 characters. Case-insensitive substring match.
`translation`	No	Translation code. Default lxx2012 (Septuagint in American English).

Output Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`translation`	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"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "book": {
+            "type": "string"
+          },
+          "chapter": {
+            "type": "integer"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verse": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "reference",
+          "text",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "translation": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "translation",
+    "results"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedNov 12, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of verses to return, 1 to 50. Default 20."

addedInput schema / properties / query / description

Added value: +"Word or phrase to find, 3 to 100 characters. Case-insensitive substring match."

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavior: canonical ordering of results and that hits include references and links. It omits one meaningful trait — there is no offset parameter, so results beyond the cap are unreachable — and "up to 50 hits" sits slightly awkwardly against the documented default of 20.

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 tightly written sentences, front-loaded with the action and matching rule. Every clause carries information and nothing is padded.

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?

An output schema exists, so return values need not be unpacked, and the description covers purpose, matching semantics, ordering, and scope adequately for a 3-parameter read tool. The remaining gap is that truncation behavior is unstated, which matters because the tool has no pagination escape hatch.

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 description coverage is 100%, with min/max, default, enum values, and matching semantics all documented in the schema itself. The description restates the substring-match rule and adds no new parameter meaning, so the baseline 3 applies.

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?

States a specific verb and resource ("Find verses") plus the matching semantics ("case-insensitive substring match") and scope ("in one translation"). The phrase "in one translation" implicitly distinguishes it from compare_translations, but no sibling is named, so an agent must infer that separation.

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?

Usage is only implied: it is clear this is for phrase lookups within a single translation. There is no explicit guidance on when to prefer compare_translations, get_passage, or find_reply_verses, and no note about what to do when results are truncated.

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?