Skip to main content
Glama

Age Calculator API - exact age in years, months, days

age_calculator
Read-onlyIdempotent

Exact age from a birth date on today or any date: years, months, days, total days and next birthday. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/age-calculator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dateOfBirth": "1990-05-17"
    },
    "name": "age_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoAge on this date (default today)
dateOfBirthYesDate of birth YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety semantics are covered. The description adds genuinely new context the annotations cannot: rate limit (25 calls/day per IP), per-call pricing, the x402 payment endpoint, and statelessness ("nothing stored"). The "files are deleted" line is a leftover template phrase since no files are accepted, which slightly muddies the disclosure.

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?

Three short sentences, front-loaded with what the tool computes and the outputs before moving to operational facts. The file-deletion sentence does not earn its place for a date-only tool and is the only wasted line.

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?

With no output schema, the description usefully enumerates the return fields, and it covers access cost and limits. Gaps remain around what "today" means across timezones and how edge cases like leap days or future birth dates behave, but for a two-parameter, low-complexity endpoint this is largely sufficient.

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 both dateOfBirth and asOf already carry descriptions, including the "default today" behavior for asOf. The description reinforces the today-or-any-date flexibility but adds no format, timezone, or boundary detail beyond the schema, making the baseline of 3 appropriate.

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?

"Exact age from a birth date on today or any date" states a specific verb and resource, and the description enumerates the returned components (years, months, days, total days, next birthday). It never names the adjacent date_calculator or business_days, so an agent must infer the boundary itself.

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 phrase "on today or any date" implies the at-date vs. today use case, but there is no explicit when-to-use statement, no exclusion, and no pointer to a sibling for related date arithmetic. The caller is left to infer that this tool is the single-purpose age computation endpoint.

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.

Resources