Skip to main content
Glama

Today's Rosary mysteries

get_rosary_mysteries
Read-onlyIdempotent

Call this when the user asks which Rosary mysteries to pray today or on a given day. Returns the mysteries for that day (Joyful Monday and Saturday, Sorrowful Tuesday and Friday, Glorious Wednesday and Sunday, Luminous Thursday), with the five mysteries, their fruits and Douay-Rheims scripture, the weekly schedule and a link to the free guided Rosary. Pass a date (YYYY-MM-DD) or a weekday; with neither, uses today in US Eastern time. Example: "What are the rosary mysteries today?"

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

Input Schema

NameRequiredDescriptionDefault
dateNoCalendar date, YYYY-MM-DD.
weekdayNoDay of the week, e.g. Wednesday.

Output Schema

NameRequiredDescriptionDefault
dateNoDate asked about, when one was given or defaulted.
weekdayNoDay of the week.
scheduleNoWeekday to mystery set, Monday to Sunday.
date_longNoLong-form date.
mystery_setNoThe set for that day: name, days it is prayed, its page, markdown and pray-now URLs, and the five mysteries with fruit and scripture.
translationNoScripture translation.
guided_rosaryNoOne-line description of the guided Rosary.
guided_rosary_urlNoLink to the free guided Rosary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 genuine context beyond that: the timezone used for "today," the full weekday-to-mystery mapping, and the shape of the returned content (five mysteries, fruits, Douay-Rheims scripture, schedule, link). No auth or rate-limit notes, but none appear relevant for a static lookup.

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 trigger condition, then inputs, then default, then an example — a sensible order with no filler. The parenthetical weekday mapping duplicates information that the output schema likely already conveys, so one clause is slightly expendable.

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 two-parameter, zero-required, read-only lookup with an output schema, nothing an agent needs is missing: trigger condition, accepted input forms, default behavior, and the nature of the result are all stated. Return-value detail is technically redundant given the output schema but harmless.

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 baseline would be 3, but the description adds real meaning beyond the schema: the two inputs are alternatives ("Pass a date ... or a weekday") and omitting both silently defaults to today in US Eastern time. That defaulting rule is not derivable from the schema alone.

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 gives a specific verb and resource ("Returns the mysteries for that day") and scopes it to a calendar day, which in practice separates it from the sibling list_rosary_mysteries. It never names that sibling, so the differentiation is implicit rather than stated.

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?

"Call this when the user asks which Rosary mysteries to pray today or on a given day" is an explicit triggering condition, and the fallback rule (today in US Eastern if nothing is passed) removes ambiguity about default behavior. No when-not guidance or named alternative is given, which keeps it below a 5.

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