Sovereign Logos Scripture

List backgrounds

list_backgrounds

Read-onlyIdempotent

Browse the Sovereign Logos background library (about 1,070 biblical images) by keyword, category, mood or reply topic, with preview URLs and the verses each image is tagged for. An id from this list is a valid background argument for create_verse_image.

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": "list_backgrounds"
  }
}

Input Schema

Name	Required	Description	Default
`mood`	No
`limit`	No
`query`	No
`topic`	No
`category`	No

Output Schema

Name	Required	Description	Default
`total`	Yes
`backgrounds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "backgrounds": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "mood": {
+            "type": "string"
+          },
+          "previewUrl": {
+            "type": "string"
+          },
+          "verses": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "previewUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "backgrounds"
+  ],
+  "type": "object"
+}

AddedNov 13, 2026

TDQS

A4.2/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, so the safety profile is covered; the description adds genuinely new context: catalog size (~1,070), that results include preview URLs and tagged verses, and that returned ids are consumable by create_verse_image. It does not disclose pagination/truncation behavior even though a limit parameter exists, which keeps it from a 5.

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, both load-bearing: the first defines the resource and gives filter axes plus return content, the second gives the downstream contract. Front-loaded with no filler or restatement of the title.

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 no full explanation, and the description still notes preview URLs and tagged verses. With five optional parameters and zero schema coverage, the missing pieces are minor (limit semantics, result ordering) but do leave small gaps for an agent deciding how to page through ~1,070 items.

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 0%, so the description must carry parameter meaning, and it does map four of five parameters to plain language ('keyword, category, mood or reply topic' → query, category, mood, topic). However it never explains 'limit' or how the filters combine, and it does not add format detail (e.g. whether query matches verse text, tags, or titles) beyond the schema.

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?

Names a specific verb+resource ('Browse the Sovereign Logos background library') and quantifies scope ('about 1,070 biblical images'). It also discloses what comes back ('preview URLs and the verses each image is tagged for'), which distinguishes it from sibling list_* tools that enumerate a different resource.

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?

Explicitly routes the agent to the downstream tool: 'An id from this list is a valid background argument for create_verse_image,' which tells the agent when this list is the prerequisite step. It gives no explicit when-not or note about using the free-text search versus the enum topic filter, so it stops short of full alternative guidance.

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?