Scientific Calculator

Age Calculator

calculator_age

Read-only

Exact age in years, months, and days from date of birth (optional reference date).

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_of_birth": "<date_of_birth>"
    },
    "name": "calculator_age"
  }
}

Input Schema

Name	Required	Description	Default
`date_of_birth`	Yes	Date of birth (YYYY-MM-DD preferred).
`reference_date`	No	Reference date; defaults to today.

Output Schema

Name	Required	Description	Default
`age`	Yes
`days`	No
`years`	Yes
`months`	No
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already establish read-only, non-destructive, closed-world behavior. The description adds that the result is broken into years, months, and days and that the reference date is optional, but it does not mention date validation, future birth dates, leap-year handling, or other behavioral edge cases.

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?

The description is a single, front-loaded sentence that states the result and the optional input with no wasted words.

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 two-parameter calculator with an output schema and annotations, the description covers the essential purpose, output granularity, and optional reference date. It could be more complete by noting validation behavior or sibling routing, but nothing critical is missing.

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 description coverage is 100%, so both parameters are already documented, including the default of today for reference_date. The description adds no syntax, format, or edge-case detail beyond what the schema already provides, making 3 the appropriate baseline.

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?

The description clearly states that it computes exact age in years, months, and days from a date of birth, which is a specific purpose. It does not explicitly distinguish itself from nearby siblings such as calculator_date_difference or calculator_days, so it falls short of a 5.

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: use it when you need an age from a birth date, optionally as of another date. There is no explicit guidance on when to prefer this over calculator_date_difference or other date-related siblings, so it remains at the minimum viable level.

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

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.