Skip to main content
Glama

Upcoming feast days

upcoming_feast_days
Read-onlyIdempotent

Lists the dated feasts, fasts and holy days in a window: Ash Wednesday, Holy Week, Easter, Ascension, Pentecost, Trinity, Christ the King, Advent, Christmas, the Epiphany, the feasts of our Lord, apostles and evangelists, with each day's color. Applies the 1979 Book of Common Prayer rules that move a feast off a Sunday or out of Holy Week and Easter Week. Optionally includes Orthodox Pascha, Julian-calendar Christmas and Reformation Day.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLength of the window in days, 1 to 400. Default 60.
fromNoFirst date of the window, YYYY-MM-DD. Defaults to today in Mountain Time.
include_saints_daysNoInclude apostles', evangelists' and other saints' days. Default true.
include_other_traditionsNoInclude Orthodox Pascha, Julian-calendar Christmas and Reformation Day. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it applies 1979 BCP transfer rules that move feasts off Sundays or out of Holy Week/Easter Week, which materially affects the output.

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, then the liturgical rules, then the optional traditions. The feast enumeration is long but earns its place by defining scope; no filler sentences.

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?

With no output schema, the description carries the return-value burden and does mention 'each day's color', hinting at output fields, though it does not describe the full record shape. Adequate for a read-only listing tool with fully documented parameters.

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 is 3. The description goes further by explaining what the optional inclusions actually mean (

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?

Opens with a specific verb and resource ('Lists the dated feasts, fasts and holy days in a window') and enumerates the concrete contents (Ash Wednesday, Holy Week, Easter, etc.). An agent can distinguish this from season_for_date or readings_for_sunday immediately.

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?

The window-based framing implies usage, but there is no explicit statement of when to choose this over season_for_date (single-date season lookup) or readings_for_sunday (lectionary readings). The agent must infer the boundary from the resource names alone.

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