Skip to main content
Glama
Sign In
OnlineCyberTools MCP (280+ filterable tools)

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

time_leap_year_checker

Read-onlyIdempotent

Check if a year is a leap year under Gregorian rules, list leap years in an inclusive range, or find the next leap years from a start year. Supports BCE years from -9999 to 9999.

Instructions

Leap Year Checker (Gregorian). Determine whether a year is a leap year under the Gregorian rule (divisible by 4, except centuries not divisible by 400), list every leap year in an inclusive year range, or find the next N leap years from a starting year. Set operation to check (with year), range (with from and to), or next (with startYear and count). Supports BCE via negative years from -9999 to 9999. Use time_date_calculator for date arithmetic and time_day_of_week for weekday lookups; this tool only answers leap-year questions. Runs locally on the integers you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the operation echo plus a data object whose shape depends on the operation (isLeap and reason for check, leapYears for range, years for next).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "time_leap_year_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationNoWhich calculation to run: check tests one year, range lists leap years between from and to, next returns the next count leap years from startYear.
yearNoYear to test (operation check only). Required for check; integer from -9999 to 9999, negative for BCE.
fromNoInclusive start year of the scan (operation range only). Must be less than or equal to to.
toNoInclusive end year of the scan (operation range only). Must be greater than or equal to from.
startYearNoFirst year considered when collecting upcoming leap years (operation next only); the start year itself is included if it is a leap year.
countNoHow many leap years to return (operation next only); integer from 1 to 50.

Output Schema

NameRequiredDescriptionDefault
operationNoThe operation that was run (check, range, or next).
dataNoOperation-specific result payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / count
      Added value: +{
+  "description": "How many leap years to return (operation next only); integer from 1 to 50.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Inclusive start year of the scan (operation range only). Must be less than or equal to to.",
+  "maximum": 9999,
+  "minimum": -9999,
+  "type": "integer"
+}
    • addedInput schema / properties / operation / description
      Added value: +"Which calculation to run: check tests one year, range lists leap years between from and to, next returns the next count leap years from startYear."
    • addedInput schema / properties / operation / enum
      Added value: +[
+  "check",
+  "range",
+  "next"
+]
    • addedInput schema / properties / startYear
      Added value: +{
+  "description": "First year considered when collecting upcoming leap years (operation next only); the start year itself is included if it is a leap year.",
+  "maximum": 9999,
+  "minimum": -9999,
+  "type": "integer"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Inclusive end year of the scan (operation range only). Must be greater than or equal to from.",
+  "maximum": 9999,
+  "minimum": -9999,
+  "type": "integer"
+}
    • addedInput schema / properties / year / description
      Added value: +"Year to test (operation check only). Required for check; integer from -9999 to 9999, negative for BCE."
    • addedInput schema / properties / year / maximum
      Added value: +9999
    • addedInput schema / properties / year / minimum
      Added value: +-9999
    • removedInput schema / required
      Removed value: -[
-  "operation",
-  "year"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Operation-specific result payload.",
+      "properties": {
+        "count": {
+          "description": "range only: number of leap years found; next only: number requested.",
+          "type": "integer"
+        },
+        "from": {
+          "description": "range only: inclusive start year of the scan.",
+          "type": "integer"
+        },
+        "isLeap": {
+          "description": "check only: true if year is a leap year.",
+          "type": "boolean"
+        },
+        "leapYears": {
+          "description": "range only: every leap year in the inclusive range, ascending.",
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        "reason": {
+          "description": "check only: which Gregorian divisibility rule decided the result.",
+          "type": "string"
+        },
+        "startYear": {
+          "description": "next only: the start year used for the search.",
+          "type": "integer"
+        },
+        "to": {
+          "description": "range only: inclusive end year of the scan.",
+          "type": "integer"
+        },
+        "year": {
+          "description": "check only: the year that was tested.",
+          "type": "integer"
+        },
+        "years": {
+          "description": "next only: the next leap years at or after startYear, ascending.",
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "operation": {
+      "description": "The operation that was run (check, range, or next).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds that the tool runs locally, is read-only, non-destructive, contacts no external service, and has a rate limit (60 req/min). This provides valuable behavioral context beyond the annotations.

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 description is a single paragraph that efficiently covers all operations, parameters, constraints, behavior, and sibling differentiation. It is front-loaded with the core purpose and avoids redundancy. Minor improvement could be structuring by operation, but it is still concise.

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?

Given the moderate complexity (three operations, six parameters, no nested objects), the description covers all necessary aspects: operations, parameter usage, constraints, behavior, rate limits, and even references the output schema. It fully equips the agent to select and invoke the tool correctly.

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

Parameters4/5

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

With 100% schema coverage, the baseline is 3. The description adds value by grouping parameters by operation (check with year, range with from and to, next with startYear and count), clarifying how parameters relate to each other beyond the schema's per-parameter descriptions.

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 clearly states the tool's purpose: determining leap years via three operations. It distinguishes from sibling tools by explicitly referencing time_date_calculator and time_day_of_week for other date-related tasks.

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 explicitly tells the agent when to use this tool vs. alternatives: 'Use time_date_calculator for date arithmetic and time_day_of_week for weekday lookups; this tool only answers leap-year questions.' It also describes the three valid operation modes and their parameter requirements.

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

Deploy Server

Other Tools