Skip to main content
Glama

Shprd Bible

Verse of the day

get_verse_of_the_day
Read-onlyIdempotent

Get Shprd's verse of the day in the World English Bible: one verse (or a short passage) chosen for each calendar day, the same one the Shprd app shows. Use this when the user asks for the verse of the day, today's verse, a daily verse, or a verse to start the morning. Pass the user's local date as date when you know it; without it, today in UTC is used. Dates more than a few days from today get a verse from a fixed rotation. Returns the reference, the exact WEB text and the credit; in hosts with cards it also shows the verse in the Shprd reader card. Do not use it to look up a specific passage (use open_bible_reader or get_bible_passage) or to search (use search_bible).

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_verse_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe calendar day as YYYY-MM-DD, e.g. "2026-11-20". Omit for today (UTC).

Output Schema

NameRequiredDescriptionDefault
dateYes
versesYes
referenceYes
attributionYes
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it discloses non-obvious behavior: the date defaults to today in UTC, dates far from today fall back to a fixed rotation, and a reader card may be rendered in some hosts. The return-value sentence (reference, WEB text, credit) is partly redundant with the existing output schema, which keeps this just short of 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.

Conciseness4/5

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

The definition is front-loaded with purpose, then trigger conditions, then parameter guidance, then exclusions. It is somewhat long, and the enumeration of trigger phrasings plus the card-rendering note add length, but nearly every sentence carries routing or behavioral information.

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?

For a single optional-parameter read tool with an output schema and full annotations, the description covers everything an agent needs: what it returns at a high level, date handling, the far-date rotation quirk, and which siblings to use instead.

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?

Schema coverage is 100%, so the format is already documented; the description still adds meaning by telling the agent to pass the user's local date when known and explaining the UTC fallback. That is guidance the schema's "Omit for today (UTC)" does not convey about which date the agent should prefer.

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 gives a specific verb and resource ("Get Shprd's verse of the day in the World English Bible") and immediately bounds the output to "one verse (or a short passage) chosen for each calendar day." It explicitly separates this from sibling tools by naming open_bible_reader, get_bible_passage and search_bible as the right tools for other tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It lists concrete trigger phrasings ("verse of the day, today's verse, a daily verse, or a verse to start the morning") and states explicit exclusions: do not use for a specific passage or for searching, with the correct alternatives named for each. An agent can route correctly without inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources