Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

time_age_calculator

Read-onlyIdempotent

Calculate exact age from a birth date to any reference date, or compute the years, months, and days between two dates. Get breakdowns, totals, and next birthday details.

Instructions

Age and Date-Span Calculator. Compute exact age or elapsed time from a birth date to a reference date (defaults to today, UTC), in proleptic-Gregorian calendar math. operation "compute" returns a years/months/days breakdown plus totals (months/weeks/days/hours/minutes/seconds), next-birthday details, the day of the week you were born, and decorative western/chinese zodiac; operation "yearsBetween" returns only the non-negative years/months/days/totalDays span between two dates. Use this for age and birthday math; use time_date_difference instead for business-day counts or for adding/subtracting a duration from a date. Runs locally via the same JS logic the page uses: read-only, non-destructive, offline-capable, rate-limited (60 req/min anonymous), no auth. Results are wrapped as operation plus data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes"compute": age/elapsed time from a birth date (needs birthYear/Month/Day; optional asOf*). "yearsBetween": span between two dates (needs from* and to*).
birthYearNoBirth year (proleptic Gregorian). Required when operation is compute.
birthMonthNoBirth month 1-12. Required when operation is compute.
birthDayNoBirth day 1-31; must be a real calendar date. Required when operation is compute.
asOfYearNoReference year for compute. Omit all asOf* to use today (UTC).
asOfMonthNoReference month 1-12 for compute. Omit all asOf* to use today (UTC).
asOfDayNoReference day 1-31 for compute. Omit all asOf* to use today (UTC).
fromYearNoStart year. Required when operation is yearsBetween.
fromMonthNoStart month 1-12. Required when operation is yearsBetween.
fromDayNoStart day 1-31. Required when operation is yearsBetween.
toYearNoEnd year. Required when operation is yearsBetween.
toMonthNoEnd month 1-12. Required when operation is yearsBetween.
toDayNoEnd day 1-31. Required when operation is yearsBetween.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe operation that was run, echoed back (compute or yearsBetween).
dataNoResult payload; shape depends on operation.
Behavior5/5

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

Adds context beyond annotations: read-only, non-destructive, offline-capable, rate-limited, no auth. No contradictions 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.

Conciseness4/5

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

Well-structured and front-loaded, but slightly verbose with repeated 'operation' phrases. Still efficient.

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?

Covers all aspects: purpose, operations, parameters, usage, behavioral traits. Output schema exists, so return values not needed.

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?

Schema coverage is 100%, so description adds limited value on parameters. It hints at required params per operation but doesn't elaborate beyond schema.

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 computes age or elapsed time with two operations, and distinguishes from sibling time_date_difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool (age/birthday math) and when to use time_date_difference instead, plus mentions local execution and rate limits.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server