Skip to main content
Glama

Season for a date

season_for_date
Read-onlyIdempotent

Returns where a date falls in the Western church year: the season (Advent, Christmas, Epiphany, Lent, Holy Week, Easter, or the season after Pentecost, also called Ordinary Time), the week of the season, the day's observance and liturgical color, the church year and its lectionary year (A, B or C), and that year's Western Easter and Orthodox Pascha. Defaults to today in Mountain Time.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD form, years 1583 to 4099. Defaults to today in Mountain Time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the default timezone (Mountain Time) and the fact that a fixed default date is used when no date is supplied, which the annotations do not convey. It stops short of describing error behavior for out-of-range 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?

It is a single sentence, front-loaded with the core purpose ('Returns where a date falls...') before the enumeration of returned fields. The long list of outputs is dense but each item earns its place because there is no output schema to carry that 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?

With no output schema, the description must shoulder the full burden of describing return values, and it does so exhaustively (season, week, observance, color, church year, lectionary year, Easter and Pascha dates). Combined with the schema's parameter documentation, an agent has everything needed to invoke it correctly and interpret the result.

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 100% and the single parameter's format (YYYY-MM-DD), valid range (1583-4099), and Mountain Time default are all already documented in the schema. The description merely repeats the default, adding no syntax or semantic detail beyond the structured field, so the baseline of 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?

The description names a specific verb and resource ('Returns where a date falls in the Western church year') and enumerates the exact data returned: season, week, observance, liturgical color, lectionary year, and Easter/Pascha dates. This is clearly distinguishable from the sibling tools (plan_sermon_series, readings_for_sunday, upcoming_feast_days), which are planning/lectionary-lookup tools rather than a single-date calendar resolver.

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?

Usage is implied by the purpose statement and the default-to-today behavior, but the description never states when to choose this over siblings like readings_for_sunday or upcoming_feast_days, nor any when-not conditions. The agent can infer intent but must reason about routing itself.

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