Skip to main content
Glama

Calculate Gregorian Easter

bpj_calendar_western_easter
Read-onlyIdempotent

Apply Gregorian ecclesiastical computus to find Western Easter Sunday.

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

Input Schema

NameRequiredDescriptionDefault
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. However, with no output schema, the description is the only place a return value could be described, and it says nothing about what comes back (a date, month/day, or formatted string). That is a meaningful gap for a computation tool.

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?

A single front-loaded sentence with no filler. It is efficient, though it spends its only words on domain jargon rather than on information the agent cannot already infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter pure-computation tool with no output schema, an agent still needs to know the form of the result and any validity constraints. The description covers neither, leaving the caller to guess what Easter Sunday is returned as.

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?

There is one parameter, and the schema supplies its type, title ('Gregorian year') and the 1600–9999 bounds, but no textual description. The description never mentions the year input or the Gregorian-only constraint, so it adds no meaning beyond the schema while the schema itself leaves the parameter without a prose description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific computation (Gregorian ecclesiastical computus) and a specific output (Western Easter Sunday), which is enough to distinguish it from the date-arithmetic siblings. The term 'computus' is domain jargon, but 'Western Easter Sunday' anchors the meaning.

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 single-purpose nature makes the intended use evident, but there is no explicit guidance such as the applicable year range or a note that this is Western (Gregorian) rather than Orthodox/Julian Easter. No alternatives are named, though the sibling list contains no obvious competing Easter tool.

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.