Sovereign Logos Scripture

Get daily post

get_daily_post

Read-onlyIdempotent

Return the Sovereign Logos daily reading for a date. The default date is today in the given timezone. The response contains post text (a "Good Morning" line, the CHRIST IS KING reading summary, and the reading page URL), the four readings from the one-year plan, and URLs for two branded card images (feed 1080x1350 PNG and story 1080x1920 PNG). Each card image includes the Sovereign Logos QR code. This tool returns that data and does not post it anywhere.

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

Input Schema

Name	Required	Description	Default
`date`	No	YYYY-MM-DD. Default: today in timezone.
`timezone`	No	IANA timezone used to decide "today" when date is omitted, e.g. America/Chicago. Default UTC, matching sovereignlogos.com/read/today.

Output Schema

Name	Required	Description	Default
`date`	Yes
`notes`	No
`images`	Yes
`pageUrl`	Yes
`postText`	Yes
`readings`	Yes
`timezone`	No
`dayNumber`	No
`summaryText`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "type": "string"
+    },
+    "dayNumber": {
+      "type": "integer"
+    },
+    "images": {
+      "properties": {
+        "feed": {
+          "properties": {
+            "contentType": {
+              "type": "string"
+            },
+            "height": {
+              "type": "integer"
+            },
+            "url": {
+              "type": "string"
+            },
+            "width": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "url"
+          ],
+          "type": "object"
+        },
+        "story": {
+          "properties": {
+            "contentType": {
+              "type": "string"
+            },
+            "height": {
+              "type": "integer"
+            },
+            "url": {
+              "type": "string"
+            },
+            "width": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "url"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "feed",
+        "story"
+      ],
+      "type": "object"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pageUrl": {
+      "type": "string"
+    },
+    "postText": {
+      "type": "string"
+    },
+    "readings": {
+      "properties": {
+        "nt": {
+          "type": "string"
+        },
+        "ot": {
+          "type": "string"
+        },
+        "proverb": {
+          "type": "string"
+        },
+        "psalm": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "ot",
+        "psalm",
+        "proverb",
+        "nt"
+      ],
+      "type": "object"
+    },
+    "summaryText": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "readings",
+    "pageUrl",
+    "postText",
+    "images"
+  ],
+  "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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description still adds real value by enumerating the response shape (post text, four readings, two card image URLs with embedded QR code) and by affirming the read-only scope in prose, though it says nothing about failure modes for invalid dates or out-of-range plan dates.

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

Conciseness4/5

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

Front-loaded with the core action and default behavior, then details the return payload. Every sentence carries information, though the enumeration of image dimensions and QR code is slightly dense and the "does not post it anywhere" line could sit earlier for faster disambiguation.

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?

Despite an output schema existing, the description's payload summary lets an agent decide whether this call satisfies its need before invoking it, and the default-date/timezone behavior is fully stated. Nothing required to call this zero-required-parameter read tool correctly is missing.

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 100% and both parameters already document YYYY-MM-DD formatting, the today default, and the IANA timezone example. The description only restates the today-in-timezone default, adding no syntax or edge-case meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Return the Sovereign Logos daily reading for a date") and immediately scopes what the response contains, so an agent can tell this apart from scripture-search tools like get_passage or search_scripture without opening the schema.

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?

Gives clear context for use (fetching the daily reading, with default date = today in the given timezone) and explicitly excludes posting behavior via "This tool returns that data and does not post it anywhere," implying create_verse_image is the separate path. It stops short of naming that sibling or stating when a specific date should be supplied instead of the default.

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?