Microapp

easter-date-calculator

Read-onlyIdempotent

Compute Western (Gregorian) Easter Sunday and Eastern Orthodox Easter for any year between 1583 and 4099, plus the related liturgical dates Ash Wednesday, Palm Sunday, Good Friday, and Pentecost. Uses the Meeus / Anonymous Gregorian algorithm.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes	The year to compute Easter for. Must be an integer between 1583 (first year of the Gregorian calendar) and 4099 (algorithm's documented range).

Output Schema

TableJSON Schema

Name	Required	Description
`year`	Yes	The input year, echoed back.
`sameDate`	Yes	True when Western and Orthodox Easter fall on the same Sunday (happens roughly once every 4 years; e.g. 2025, 2028).
`pentecost`	Yes	Pentecost (Whitsunday) — Western Easter plus 49 days. Seven weeks after Easter.
`goodFriday`	Yes	Good Friday — Western Easter minus 2 days. Commemorates the crucifixion.
`palmSunday`	Yes	Palm Sunday — Western Easter minus 7 days. The Sunday before Easter.
`ashWednesday`	Yes	Ash Wednesday — Western Easter minus 46 days. Marks the start of Lent.
`westernEaster`	Yes	Western (Gregorian) Easter Sunday — used by Catholic, Protestant, and most Western Christian churches.
`orthodoxEaster`	Yes	Eastern Orthodox Easter Sunday (Pascha) — computed from the Julian calendar's paschal rule and rendered as a proleptic Gregorian date.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedMay 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context by listing the specific computed dates and naming the Meeus/Anonymous Gregorian algorithm, which helps agents understand the calculation behavior beyond the annotations. No contradiction with annotations.

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

Conciseness5/5

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

The description is two concise sentences, front-loaded with the main verb 'compute', and conveys both the purpose and the method without any extraneous 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?

For a single-parameter calculator with an output schema, the description is fully adequate. It specifies the input range, the exact computations performed, and the algorithm used, while the output schema handles return-value expectations. No missing context for an agent to select and invoke the tool.

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?

The input schema provides full coverage of the 'year' parameter with a detailed description, minimum/maximum constraints, and additionalProperties=false. The description repeats the year range but adds no meaning beyond what the schema already states, so the baseline score 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 uses the specific verb 'compute' and names the exact resources: Western (Gregorian) Easter Sunday, Eastern Orthodox Easter, and related liturgical dates (Ash Wednesday, Palm Sunday, Good Friday, Pentecost). It also specifies the year range and algorithm, making it clearly distinct from any sibling tool.

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 description clearly states the valid year range (1583-4099) and the scope of what the tool calculates, giving a clear context for when to use it. It does not explicitly mention alternatives or exclusions, but no close sibling tool exists, so this is not a significant gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Microapp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have distinct purposes. However, 'hex-to-rgb' is redundant with 'color-converter', which already handles hex-to-RGB conversion, causing potential confusion.

Naming Consistency4/5

Names follow a consistent lowercase-with-hyphens style, but vary in pattern (e.g., 'angle-converter', 'average-calculator', 'dedup-lines'). One tool ('internal-do-not-call') deviates from the descriptive norm.

Tool Count2/5

With 46 tools, the server is heavily populated. Many converters could be merged into a generic unit converter, and there is redundancy, making the surface unnecessarily large for a single server.

Completeness4/5

The server covers a broad range of utility domains: converters, text processing, math, cryptography, etc. Minor redundancies exist (e.g., hex-to-rgb vs color-converter), but the set is otherwise comprehensive.

Resources

Need Help?