Skip to main content
Glama

La Iglesia Católica de los Agentes de AI

Liturgical calendar

liturgical_calendar
Read-onlyIdempotent

{"use_when":{"en":"Use when someone asks which liturgical season, color or feast it is, or when Easter, Lent or Advent fall.","es":"Úsala cuando pregunten qué tiempo litúrgico, color o fiesta es, o cuándo caen Pascua, Cuaresma o Adviento."},"what":{"en":"Liturgical season, week, color, celebration and the year's movable feasts for a date (Roman calendar).","es":"Tiempo, semana, color, celebración y fiestas móviles del año."}}

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD. Omit for today in Europe/Berlin; any other value (today, hoy, 2026/11/08, empty) is an error / Fecha AAAA-MM-DD; sin fecha, hoy en Berlín
langNoLanguage / Idioma: es (default), en, ites

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Date YYYY-MM-DD (default: today in Europe/Berlin) / Fecha (por defecto hoy en Berlín)"New value: +"Date YYYY-MM-DD. Omit for today in Europe/Berlin; any other value (today, hoy, 2026/11/08, empty) is an error / Fecha AAAA-MM-DD; sin fecha, hoy en Berlín"
  2. 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, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds useful scope the annotations don't: the Roman calendar limitation and the fact that the response includes the year's movable feasts, not just a single day's data. It does not mention error behavior for malformed dates, but the schema covers that.

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

Conciseness3/5

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

The content is short and every clause carries information, but it is delivered as a serialized JSON object with fully duplicated Spanish and English text, which doubles length and buries the key clause behind structural syntax rather than front-loading it as prose. It is efficient in substance but awkwardly packaged.

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 only two optional parameters, rich schema documentation and no output schema, the description does the necessary extra work of enumerating what is returned (season, week, color, celebration, movable feasts) and noting the Roman-calendar scope. An agent could call this correctly from the definition alone; only the malformed-date error behavior is left implicit.

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%, with the date format pattern, the 'omit for today in Europe/Berlin' default and the lang enum all documented in the schema itself. The description only says results are 'for a date' and never elaborates on format or language behavior, so it adds nothing beyond the schema and 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?

The 'what' field names the exact resource: liturgical season, week, color, celebration and the year's movable feasts for a given date, scoped to the Roman calendar. This is specific enough to distinguish it from siblings like saint_of_the_day, mass_of_the_day and readings_of_the_day without opening any 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?

The 'use_when' field gives concrete trigger questions ('which liturgical season, color or feast it is', 'when Easter, Lent or Advent fall'), so an agent knows exactly when to reach for it. It stops short of naming exclusions or pointing to alternative tools for adjacent queries (e.g. daily readings), so it is clear context without explicit routing.

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