Skip to main content
Glama

Fecha de Pascua

easter-sunday
Read-onlyIdempotent

Calcula el Domingo de Pascua occidental y ortodoxo y fechas relacionadas (Miércoles de Ceniza, Jueves y Viernes Santo, Pentecostés…). Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: listar los 18 (hasta 2025) o 19 (desde 2026) festivos nacionales de Colombia de un año (co-holidays). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Computes Western (Gregorian computus) and Orthodox Easter Sunday for a year 1583-4099, plus related Western dates: Ash Wednesday, Palm Sunday, Holy Thursday, Good Friday, Ascension, Pentecost, Corpus Christi. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). [EN completo / full EN: inputSchema.description]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "easter-sunday"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (integer; required; min 1583; max 4099).

Output Schema

NameRequiredDescriptionDefault
westernNo
orthodoxNo
ascensionNo
pentecostNo
good_fridayNo
palm_sundayNo
ash_wednesdayNo
holy_thursdayNo
corpus_christiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"EN: Computes Western (Gregorian computus) and Orthodox Easter Sunday for a year 1583-4099, plus related Western dates: Ash Wednesday, Palm Sunday, Holy Thursday, Good Friday, Ascension, Pentecost, Corpus Christi. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: listing the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (co-holidays). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."New value: +"EN: Computes Western (Gregorian computus) and Orthodox Easter Sunday for a year 1583-4099, plus related Western dates: Ash Wednesday, Palm Sunday, Holy Thursday, Good Friday, Ascension, Pentecost, Corpus Christi. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: listing the 18 (until 2025) or 19 (from 2026) Colombian national holidays for a year (co-holidays). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  2. Changed1 schema field changed
    • addedInput schema / properties / year / examples
      Added value: +[
      +  2026
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Computes Western (Gregorian computus) and Orthodox Easter Sunday for a year 1583-4099, plus related Western dates: Ash Wednesday, Palm Sunday, Holy Thursday, Good Friday, Ascension, Pentecost, Corpus Christi. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: listing the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (co-holidays). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description goes beyond that by disclosing operational traits not in the annotations: no network access, no stored state, determinism of output, and hard limits (64 KB input, 1 s per call, 1 MB result), which directly helps an agent budget and retry correctly.

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 text is front-loaded with the computation, then usage, exclusions, side effects and limits in a scannable labeled structure. It loses a point for redundancy: the Spanish and English blocks repeat the same content, and the full English string is duplicated verbatim inside inputSchema.description.

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?

An output schema exists, so return-value detail is not required, and the definition covers input range, exclusions, side effects and resource limits. The only weak spot is that the 'When' clause emphasizes time zones and DST, which are not really relevant to computus dates, a minor framing mismatch rather than a gap.

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 there is a single parameter whose type, requiredness and 1583-4099 bounds are already in the schema. The description restates the year range but adds no syntax, format or edge-case semantics (e.g. how Orthodox vs Western output is labeled) beyond structured data, 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 computation (Western Gregorian and Orthodox Easter Sunday plus related feast dates) and bounds it to years 1583-4099, so the resource is unambiguous. It also explicitly distinguishes itself from the co-holidays sibling by saying it is not for listing Colombian national holidays, letting an agent separate the two without opening schemas.

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 provides an explicit 'When' clause (when any date/calendar result must be exact — offsets, DST, month ends, leap years) and an explicit 'No para / Not for' clause naming the alternative tool for national holiday listing. Both the positive trigger and the exclusion are stated, leaving nothing to infer.

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