Skip to main content
Glama

Resolve a next anniversary

bpj_calendar_anniversary
Read-onlyIdempotent

Find the next anniversary on or after a reference date, observing February 29 on February 28 in common years.

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": {
      "date": "<date>",
      "end": "<end>"
    },
    "name": "bpj_calendar_anniversary"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/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 does add one genuinely non-obvious rule (Feb 29 resolves to Feb 28 in common years), which is real value, but it says nothing about the required "end" bound or what a same-day hit returns.

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 well-formed sentence with the leap-day caveat front-loaded after the core behaviour; nothing is wasted. It is arguably too short rather than too long, but structurally sound.

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

Completeness3/5

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

For a two-parameter pure-computation tool with no output schema, the definition should say what comes back (a date string? an object?) and how "end" bounds the search. Neither appears, leaving an agent to guess before it can invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and it only half-delivers. It explains "date" as the reference date, but the required "end" parameter is never mentioned and no date string format (e.g. YYYY-MM-DD, hinted only by maxLength 10) is given.

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 verb and resource ("Find the next anniversary") plus scope ("on or after a reference date"), so the intent is unambiguous. It doesn't differentiate itself from neighbouring calendar resolvers such as bpj_calendar_nth_weekday or bpj_calendar_date_series, which keeps it out of 5 territory.

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 description implies a recurring-anniversary use case but never states when to pick this tool over the adjacent calendar helpers, nor any preconditions. Guidance is inferable but not written down.

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.