Skip to main content
Glama

List Gregorian leap years

bpj_calendar_common_leap_list
Read-onlyIdempotent

Apply the Gregorian 4-, 100- and 400-year rules to list leap years in a bounded period.

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>",
      "span": "<span>"
    },
    "name": "bpj_calendar_common_leap_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
spanYes
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the genuinely useful behavioral fact that the Gregorian 4/100/400 rule set is applied, but says nothing about whether the start year is included, how the period is bounded at the upper limit, or what the result looks like.

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?

One compact sentence with the algorithm and the scope front-loaded and no filler. Nothing could be removed without losing substance.

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?

For a simple, fully annotated, two-parameter read tool with no output schema, the definition covers purpose and algorithm adequately. The remaining gap is boundary semantics on the range and result format, which is modest given the tool's low complexity.

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 must carry the parameter meaning. 'Gregorian' reinforces the year parameter and 'bounded period' hints that year and span combine into a range, but inclusiveness of the start year, whether span counts forward from year or from year+1, and behavior at the 400-year cap are all left ambiguous even though the schema only offers bare titles.

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?

States a specific verb ('list') and resource ('leap years') with the determining algorithm ('Gregorian 4-, 100- and 400-year rules') and a scope ('bounded period'). That is enough to separate it from calendar siblings that produce date series, weekdays, or bounds, though it never names an alternative.

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?

Usage is implied: call this when you need the set of leap years inside a range. There is no explicit when-to-use, when-not-to-use, or pointer to sibling tools such as the date-series or weekday tools, so the agent must infer selection criteria.

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.